This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: [rfc/remote] Tell remote stubs which signals are boring
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: gdb at sourceware dot org
- Date: Thu, 26 Oct 2006 02:57:29 -0400
- Subject: Re: [rfc/remote] Tell remote stubs which signals are boring
- References: <20061025212441.GA622@nevyn.them.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Wed, 25 Oct 2006 17:24:41 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> This is the solution I came up with for that problem, adjusted to HEAD
> and given a more sensible packet name. I have a tested implementation
> of this patch for HEAD, if my remote protocol choices are acceptable.
> The new mechanism is completely transparent to the user.
I'm confused: shouldn't this packet be automatically sent to a remote
target when I say, e.g., "handle SIGALRM nostop noprint pass"? Am I
missing something?