Bug 118383 - objdump -g does not print debugging info
objdump -g does not print debugging info
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: binutils (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Depends On:
  Show dependency treegraph
Reported: 2004-03-16 00:38 EST by abhijit karmarkar
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-03-16 06:41:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description abhijit karmarkar 2004-03-16 00:38:41 EST
Description of problem: 
objdump -g <objectfile> does not print debugging info.

Version-Release number of selected component (if applicable):
RHEL3 AS, Update 1.

How reproducible:

Steps to Reproduce:
1. compile any C program with "-g" (gcc -g -o foo foo.c)
2. try dumping debugging info: objdump -g foo
Actual results:
objdump: foo: no recognized debugging information

Expected results:
objdump should print debugging (stabs) info.
i am especially interested in struct info (size, member offsets etc.)

looks that gcc3 does not have a .stabs ELF section. and that
makes objdump believe that there is no debugging information.

Additional info:
this happens with gcc 3.2 and binutils w/ RHEL3 Update 1.
gcc version: gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-24)
binutils   :
objdump ver: GNU objdump 20030523
Comment 1 Jakub Jelinek 2004-03-16 06:41:28 EST
Please read the manual page of objdump:
"-g ... Only certain types of debugging information have been
implemented.  Some other types are supported by `readelf -w'."

Particularly, DWARF2 which now GCC emits by default is supported
only by readelf -w[liaprmfFso].

Note You need to log in before you can comment on or make changes to this bug.