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: stabs at function entry point?

From: John Levon <levon at movementarian dot org>
To: gcc at gcc dot gnu dot org
Date: Wed, 13 Mar 2002 22:07:32 +0000
Subject: Re: stabs at function entry point?
References: <20020313131156.A24576@redhat.com> <639A9316-36CD-11D6-958B-003065C86F94@apple.com>

On Wed, Mar 13, 2002 at 01:58:02PM -0800, Dale Johannesen wrote:

> Yes, that is what happens now.  As a result, when you set a breakpoint
> on a function, gdb (ours, anyway) stops at the first insn rather than
> after the prologue, which means the parameters and stack traceback
> don't show correctly.  Are you implying this should be fixed in gdb?
> That was my first impression, but Jim convincingly argued otherwise.

there are other users of debug entries than gdb ...

regards
john

-- 
I am a complete moron for forgetting about endianness. May I be
forever marked as such.

Follow-Ups:
- Re: stabs at function entry point?
  - From: Dale Johannesen

References:
- Re: stabs at function entry point?
  - From: Richard Henderson
- Re: stabs at function entry point?
  - From: Dale Johannesen

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