This is the mail archive of the gdb@sourceware.cygnus.com mailing list for the GDB project.

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

Re: debugging inline functions

To: Mark Mitchell <mark at codesourcery dot com>
Subject: Re: debugging inline functions
From: Jason Merrill <jason at cygnus dot com>
Date: 29 Nov 1999 13:31:15 -0800
Cc: per at bothner dot com, gcc at gcc dot gnu dot org, gdb at sourceware dot cygnus dot com
References: <m2u2m766gs.fsf@magnus.bothner.com> <19991128135119Y.mitchell@codesourcery.com> <m2hfi62rqe.fsf@magnus.bothner.com> <19991128160007P.mitchell@codesourcery.com>

 Per> Still, that is a user-interface issue - i.e.
 Per> a gdb issue.  We should make sure the debug output emits
 Per> enough information so that the debugger can (in theory)
 Per> present the call/inline state clearly.  I agree that suggests
 Per> emiting the inlined callee's line numbers.  But we should
 Per> also emit some indication that the function *was* inlined.
 Per> Does dwarf2 have a defined way to do this?  If so, I'd like
 Per> Gcc to emit it.  -- --Per Bothner per@bothner.com

GCC already does emit it (in dwarf2).  GDB just doesn't use the information.

Jason

References:
- debugging inline functions
  - From: Per Bothner
- Re: debugging inline functions
  - From: Mark Mitchell
- Re: debugging inline functions
  - From: Per Bothner
- Re: debugging inline functions
  - From: Mark Mitchell

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