This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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]

Re: RFC: debug line info & inlining; patch proposal and request forcomments.


Carlo Wood wrote:
The debug source-file/line-number information (location) in relation
with inlined functions is not perfect.

The primary place for tests of this kind is in the gdb testsuite. If you make changes to debug info, you have to make sure that the gdb testsuite doesn't break. This may mean patches for the gdb testsuite if you want to change behaviour visible to it, or add tests to it. This may need to be discussed with the gdb team.


You are apparently using stabs. DWARF2 is preferred. If DWARF2 gives the right answer, then maybe the solution is to use DWARF2 instead of stabs. If you are changing code outside dbxout.c, then make sure you don't accidentally break the DWARF2 output, since people will be unhappy if stabs gets better at the expense of DWARF2.

This does look like a reasonable change to the debug info. I'm not enough of a C++ expert to comment on the right testcase for the change.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]