From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: FYI: add missing debug_linux_nat
Date: Wed, 17 Mar 2010 16:16:00 -0000 [thread overview]
Message-ID: <m31vfi9b4o.fsf@fleche.redhat.com> (raw)
I'm checking this in.
I saw a strange message today:
LND: Sending signal 11 to process 13765
This is caused by a missing test of debug_linux_nat. Thanks to Pedro
for pointing out the linux-nat.c debugging print convention.
Tom
2010-03-17 Tom Tromey <tromey@redhat.com>
* linux-nat.c (linux_nat_detach): Check debug_linux_nat.
Index: linux-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/linux-nat.c,v
retrieving revision 1.164
diff -u -r1.164 linux-nat.c
--- linux-nat.c 24 Feb 2010 17:01:57 -0000 1.164
+++ linux-nat.c 17 Mar 2010 16:14:01 -0000
@@ -1783,10 +1783,11 @@
pass it along with PTRACE_DETACH. */
args = alloca (8);
sprintf (args, "%d", (int) WSTOPSIG (status));
- fprintf_unfiltered (gdb_stdlog,
- "LND: Sending signal %s to %s\n",
- args,
- target_pid_to_str (main_lwp->ptid));
+ if (debug_linux_nat)
+ fprintf_unfiltered (gdb_stdlog,
+ "LND: Sending signal %s to %s\n",
+ args,
+ target_pid_to_str (main_lwp->ptid));
}
delete_lwp (main_lwp->ptid);
next reply other threads:[~2010-03-17 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 16:16 Tom Tromey [this message]
2010-03-17 17:31 ` Tom Tromey
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=m31vfi9b4o.fsf@fleche.redhat.com \
--to=tromey@redhat.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