From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: QPassSignals patch to go with proposed protocol
Date: Thu, 16 Nov 2006 15:13:00 -0000 [thread overview]
Message-ID: <20061116151307.GA10461@nevyn.them.org> (raw)
In-Reply-To: <uslgkh8wv.fsf@gnu.org>
On Wed, Nov 15, 2006 at 08:17:04PM +0200, Eli Zaretskii wrote:
> This is okay with me, thanks.
Thanks, checked in. Since we just got a query about this functionality
on gdb@ (ironic - first one I can remember seeing, half a day before
checking it in) I wonder if it ought to be mentioned in NEWS, as
attached?
--
Daniel Jacobowitz
CodeSourcery
2006-11-16 Daniel Jacobowitz <dan@codesourcery.com>
* NEWS: Mention QPassSignals.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.199
diff -u -p -r1.199 NEWS
--- NEWS 14 Nov 2006 21:53:59 -0000 1.199
+++ NEWS 16 Nov 2006 15:12:31 -0000
@@ -21,6 +21,9 @@ broken in GDB 6.3, 6.4, and 6.5.
* Support for GNU/Linux Thread Local Storage (TLS, per-thread variables) no
longer requires symbolic debug information (e.g. DWARF-2).
+* The GDB remote stub, gdbserver, now has lower overhead for high
+frequency signals (e.g. SIGALRM) via the QPassSignals packet.
+
* New commands
set substitute-path
@@ -59,6 +62,10 @@ qXfer:auxv:read:
Fetch an OS auxilliary vector from the remote stub. This packet is a
more efficient replacement for qPart:auxv:read.
+QPassSignals:
+ Ignore the specified signals; pass them directly to the debugged program
+ without stopping other threads or reporting them to GDB.
+
* Removed remote packets
qPart:auxv:read:
next prev parent reply other threads:[~2006-11-16 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 21:28 Daniel Jacobowitz
2006-10-26 6:55 ` Eli Zaretskii
2006-10-26 12:33 ` Daniel Jacobowitz
2006-10-27 8:11 ` Eli Zaretskii
2006-11-14 22:35 ` Daniel Jacobowitz
2006-11-15 18:17 ` Eli Zaretskii
2006-11-16 15:13 ` Daniel Jacobowitz [this message]
2006-11-16 20:12 ` Eli Zaretskii
2006-11-17 17:49 ` 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=20061116151307.GA10461@nevyn.them.org \
--to=drow@false.org \
--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