From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: [RFA] NEWS entry for gdbserver support for debugging without libthread_db
Date: Tue, 23 Oct 2007 20:28:00 -0000 [thread overview]
Message-ID: <20071023201005.GB2370@caradoc.them.org> (raw)
Eli, is this OK?
--
Daniel Jacobowitz
CodeSourcery
2007-10-23 Daniel Jacobowitz <dan@codesourcery.com>
* NEWS: Mention gdbserver support for non-libthread_db operation.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.244
diff -u -p -r1.244 NEWS
--- NEWS 21 Oct 2007 10:27:49 -0000 1.244
+++ NEWS 23 Oct 2007 20:04:08 -0000
@@ -18,6 +18,9 @@ and in inlined functions.
* The GDB remote stub, gdbserver, now supports the AltiVec and SPE
registers on PowerPC targets.
+* The GDB remote stub, gdbserver, now supports thread debugging on GNU/Linux
+targets even when the libthread_db library is not available.
+
*** Changes in GDB 6.7
* Resolved 101 resource leaks, null pointer dereferences, etc. in gdb,
next reply other threads:[~2007-10-23 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 20:28 Daniel Jacobowitz [this message]
2007-10-23 20:53 ` Eli Zaretskii
2007-10-24 20:58 ` 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=20071023201005.GB2370@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.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