This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Stepping over longjmp presumably broken for glibc
- From: Jim Blandy <jimb at red-bean dot com>
- To: Mark Kettenis <mark dot kettenis at xs4all dot nl>, gdb at sourceware dot org
- Date: Sun, 1 Jan 2006 21:25:14 -0800
- Subject: Re: Stepping over longjmp presumably broken for glibc
- References: <uk6dvivxw.fsf@gnu.org> <uek43iu5a.fsf@gnu.org> <20051224162302.GA11929@nevyn.them.org> <uirtezc3i.fsf@gnu.org> <8f2776cb0512252006i4b28abe7if0fd67dd8cee6f10@mail.gmail.com> <ur7808mft.fsf@gnu.org> <8f2776cb0512262024n39deb5e9q64ab62c48652e336@mail.gmail.com> <20051230023830.GA26004@nevyn.them.org> <200512300932.jBU9WBn6015669@elgar.sibelius.xs4all.nl> <20051230162507.GA5006@nevyn.them.org>
On 12/30/05, Daniel Jacobowitz <drow@false.org> wrote:
> That's not what I meant - I meant between a longjmp with "normal"
> unwind information, or with Jim's proposed "magic" unwind information
> that returned to the setjmp target. There's got to be at least one of
> the former out there somewhere...
Why do you need to? If I'm thinking this through right, once longjmp
is annotated this way, GDB has no further work to do. The bug is
"fixed", just not in GDB.