This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [rfc] dwarf2 backtrace from setcontext
- From: Richard Henderson <rth at redhat dot com>
- To: Andreas Jaeger <aj at suse dot de>, Jakub Jelinek <jakub at redhat dot com>, Glibc hackers <libc-hacker at sources dot redhat dot com>, gdb at gcc dot gnu dot org
- Date: Mon, 12 Jan 2004 15:52:17 -0800
- Subject: Re: [rfc] dwarf2 backtrace from setcontext
- References: <m3isji92u3.fsf@gromit.moeb> <20040111025223.A2564@redhat.com> <m3eku692mz.fsf@gromit.moeb> <m37jzy92hr.fsf@gromit.moeb> <20040111030005.C13258@redhat.com> <m3wu7y7k7j.fsf@gromit.moeb> <20040111202020.GB24540@redhat.com> <m3hdz2i60i.fsf@gromit.moeb> <20040111213631.GD24540@redhat.com> <20040112231919.GB27775@nevyn.them.org>
On Mon, Jan 12, 2004 at 06:19:19PM -0500, Daniel Jacobowitz wrote:
> It seems to me that the best solution would be a new rule, either
> val_expression(E) or the simpler val_cfa_offset(N). Then the unwind
> information can accurately describe the stack pointer.
That would certainly work for me.
> That would probably work for this example - I can't see any reason that
> GDB would care. And for setcontext it makes a certain sense, since you
> do seem to have "fallen through" into a different backtrace.
I'll recommend we do that for glibc then.
r~