Skip to content

Commit

Permalink
debugging: slides: clarify debug_info absence reason on embedded systems
Browse files Browse the repository at this point in the history
Fixes #153

Signed-off-by: Alexis Lothoré <[email protected]>
  • Loading branch information
Tropicao committed Jan 3, 2025
1 parent fe06d53 commit fb4aaa8
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions common/gdb.tex
Original file line number Diff line number Diff line change
Expand Up @@ -152,10 +152,10 @@ \subsection{Remote debugging}
\item In a non-embedded environment, debugging takes place using \code{gdb}
or one of its front-ends.
\item \code{gdb} has direct access to the binary and libraries compiled
with debugging symbols.
\item However, in an embedded context, the target platform
environment is often too limited to allow direct debugging with
\code{gdb} (2.4 MB on x86).
with debugging symbols, which is often false for embedded systems
(binaries are stripped, without debug\_info) to save storage space.
\item For the same reason, embedding the \code{gdb} program on embedded
targets is rarely desirable (2.4 MB on x86).
\item Remote debugging is preferred
\begin{itemize}
\item \code{ARCH-linux-gdb} is used on the development workstation, offering
Expand Down

0 comments on commit fb4aaa8

Please sign in to comment.