This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I posted about this a while ago but we're running into it again. Apparently it appeared to work with GCC 3.3.5 because we use dwarf-2 as the default instead of stabs. With stabs debugging addr2line seems to walk backward in the code as far as it has to in order to find line number information. The net effect is that if you ask for the line number of an address inside a function that was linked in from a static lib that didn't have debug info you will get the source file and line number of whatever the last debug info is before that address. With dwarf-2 you get '??:0'. As a first step we only need to know if this is expected from stabs or if this is a bug. I have confirmed this behaviour with the 2.16 binutils on Fedora Core 2 with GCC 3.3.3 as well as on Neutrino with GCC 3.3.5. I have attached a test case as well.
Attachment:
stabs_testcase.tgz
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |