From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Updates support for breakpoints that generate SIGILL
Date: Fri, 29 Jan 2010 04:10:00 -0000 [thread overview]
Message-ID: <20100129040933.GC26827@adacore.com> (raw)
In-Reply-To: <20100128215914.GB2813@caradoc.them.org>
> Any thoughts about this patch, or shall I check it in? Tested on
> arm-linux-gnueabi using gdbserver, both with and without SIGILLs.
I agree that the patch is useful - someone else might need the same
functionality later on too.
> 2010-01-28 Daniel Jacobowitz <dan@codesourcery.com>
>
> gdb/
> * infrun.c (prepare_to_proceed): Handle other signals which might
> match a breakpoint.
> (handle_inferior_event): Move the check for unusual breakpoint
> signals earlier.
>
> gdb/gdbserver/
> * linux-low.c (get_stop_pc): Check for SIGTRAP.
> (linux_wait_for_event_1): Handle SIGILL and SIGSEGV as possible
> breakpoints.
--
Joel
next prev parent reply other threads:[~2010-01-29 4:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 21:59 Daniel Jacobowitz
2010-01-29 4:10 ` Joel Brobecker [this message]
2010-01-29 15:40 ` Daniel Jacobowitz
2010-02-08 19:35 ` Ulrich Weigand
2010-02-08 19:45 ` Daniel Jacobowitz
2010-02-08 19:51 ` Ulrich Weigand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100129040933.GC26827@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox