This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [commit+7.5] [patchv2] Write bpt at the ON_STACK bpt address
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Sergio Durigan Junior <sergiodj at redhat dot com>, Edjunior Barbosa Machado <emachado at linux dot vnet dot ibm dot com>, Jan Kratochvil <jan dot kratochvil at redhat dot com>, Philippe Waroquiers <philippe dot waroquiers at skynet dot be>, Joel Brobecker <brobecker at adacore dot com>, gdb-patches at sourceware dot org, "Maciej W. Rozycki" <macro at codesourcery dot com>
- Date: Fri, 03 Aug 2012 08:22:47 -0600
- Subject: Re: [commit+7.5] [patchv2] Write bpt at the ON_STACK bpt address
- References: <5012B1B6.1030003@redhat.com> <1343339398.2258.119.camel@soleil> <20120727184633.GA14182@host2.jankratochvil.net> <20120731073643.GA18696@host2.jankratochvil.net> <501B03E4.1020209@linux.vnet.ibm.com> <m3vch0gacz.fsf@redhat.com> <501B2271.6030406@redhat.com>
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> Curious. But is the cause the same? If something sending C-c to gdb
Pedro> at the "wrong" time?
It could be any exception thrown at the wrong spot in any sniffer.
It would be interesting to know exactly where the original exception is
thrown. I am still not sure that my fix is the correct one. Maybe it
really is better to fix the sniffers. Or maybe do both.
Tom