This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: stabs at function entry point?
- From: Geoff Keating <geoffk at geoffk dot org>
- To: jingham at apple dot com
- Cc: dalej at apple dot com, gcc at gcc dot gnu dot org
- Date: Wed, 13 Mar 2002 17:29:51 -0800
- Subject: Re: stabs at function entry point?
- References: <60F9D214-36D0-11D6-95FF-000393540DDC@apple.com>
- Reply-to: Geoff Keating <geoffk at redhat dot com>
> Date: Wed, 13 Mar 2002 14:19:26 -0800
> Cc: Geoff Keating <geoffk@geoffk.org>, gcc@gcc.gnu.org
> From: Jim Ingham <jingham@apple.com>
> Right, the only odd thing that happens is that if you do
>
> (gdb) info line *&function
>
> the line number returned is actually the last line of the previous
> function. While this is wrong, I don't think this is anywhere near as
> wrong as breaking on the line where the function is defined, and having
> it stop with the stack all wrong, etc... If you are stopping in the
> prologue, you are probably NOT doing source line debugging, after all.
> So why would you really care exactly what line this is?
... because if I am debugging a core dump, and I see that it's crashed
on the last line of some function, and it really crashed on the first
line of some other function, I'm likely to be confused.
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>