RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

More information on what symbolic information is for and

Browse Source 
how to get it from a file other thatn the executable.
This commit is contained in:
Joel Sherrill
2000-05-04 20:25:57 +00:00
parent 104a48d400
commit 49963428d7
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
doc/FAQ/debug.t
View File

@@ -54,6 +54,19 @@ In this case, it is not uncommon to see executable files
that are between two and three times larger than the actual
space required in target memory.
Remember, the debugging information is required to do symbolic
debugging with gdb. Normally gdb obtains its symbolic information
from the same file that it gets the executable image from. However,
gdb does not require that the executable image and symbolic
information be obtained from the same file. So you might
want to create a @code{hello_with_symbols.exe}, copy that
file to @code{hello_without_symbols.exe}, and strip
@code{hello_without_symbols.exe}. Then gdb would have to
be told to read symbol information from @code{hello_with_symbols.exe}.
The gdb command line option @code{-symbols} or command
@code{symbol-file} may be used to specify the file read
for symbolic information.
@section Malloc