From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: [rfc/remote] Tell remote stubs which signals are boring
Date: Thu, 26 Oct 2006 06:57:00 -0000 [thread overview]
Message-ID: <E1GczBB-0006Wu-9h@fencepost.gnu.org> (raw)
In-Reply-To: <20061025212441.GA622@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 25 Oct 2006 17:24:41 -0400)
> 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?
next prev parent reply other threads:[~2006-10-26 6:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 21:24 Daniel Jacobowitz
2006-10-25 21:33 ` Mark Kettenis
2006-10-25 22:56 ` David Daney
2006-10-26 1:40 ` Daniel Jacobowitz
2006-10-26 7:02 ` Eli Zaretskii
2006-10-26 6:57 ` Eli Zaretskii [this message]
2006-10-26 12:18 ` Daniel Jacobowitz
2006-10-26 15:01 ` Eli Zaretskii
2006-10-26 15:10 ` Daniel Jacobowitz
2006-10-26 15:18 ` Eli Zaretskii
2006-10-26 15:22 ` Daniel Jacobowitz
2006-10-26 15:27 ` Mark Kettenis
2006-10-26 15:37 ` Daniel Jacobowitz
2006-10-26 17:54 ` Mark Kettenis
2006-10-26 21:11 ` Jim Blandy
2006-10-26 21:16 ` Daniel Jacobowitz
2006-10-26 21:28 ` Jim Blandy
2006-10-26 21:37 ` Daniel Jacobowitz
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=E1GczBB-0006Wu-9h@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@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