Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [NEWS] Mention signal info inspection support
Date: Fri, 06 Feb 2009 23:39:00 -0000	[thread overview]
Message-ID: <200902062339.21716.pedro@codesourcery.com> (raw)

Eli, does this look OK?

-- 
Pedro Alves


2009-02-06  Pedro Alves  <pedro@codesourcery.com>

	* NEWS: Mention inspecting extra signal information, $_siginfo,
	and the qXfer:siginfo:read and qXfer:siginfo:write packets.

---
 gdb/NEWS |    8 ++++++++
 1 file changed, 8 insertions(+)

Index: src/gdb/NEWS
===================================================================
--- src.orig/gdb/NEWS	2009-02-06 23:13:17.000000000 +0000
+++ src/gdb/NEWS	2009-02-06 23:28:25.000000000 +0000
@@ -26,6 +26,10 @@ completions will be "f1" and "f2".
 operators when expanding macros.  It also supports variable-arity
 macros.
 
+* GDB now supports inspecting extra signal information, exported by
+  the new $_siginfo convenience variable.  The feature is currently
+  implemented on linux ARM, i386 and amd64.
+
 * New remote packets
 
 qSearch:memory:
@@ -39,6 +43,10 @@ QStartNoAckMode
 qXfer:osdata:read
   Obtains additional operating system information
 
+qXfer:siginfo:read
+qXfer:siginfo:write
+  Read or write additional signal information.
+
 * Removed remote protocol undocumented extension
 
   An undocumented extension to the remote protocol's `S' stop reply


             reply	other threads:[~2009-02-06 23:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 23:39 Pedro Alves [this message]
2009-02-07  9:23 ` Eli Zaretskii
2009-02-07 15:01   ` Pedro Alves

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=200902062339.21716.pedro@codesourcery.com \
    --to=pedro@codesourcery.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