From: "Patrick Monnerat" <Patrick.Monnerat@datasphere.ch>
To: "Keith Seitz" <keiths@redhat.com>
Cc: <insight@sourceware.org>
Subject: RE: [PATCH] fix error sending signal to dead process
Date: Thu, 19 Apr 2012 15:19:00 -0000 [thread overview]
Message-ID: <AB5E58B87EB73C46A38073D8F459F113D9F89A@dataspheresrv01> (raw)
In-Reply-To: <4F8F5AAD.9050207@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
Keith Seitz wrote:
> There should be spaces between function names and opening parenthesis.
> [Yeah, it's rather lame, but it is GNU coding standard. Insight
follows GDB's conventions.]
> ChangeLog entry?
The new attached patch fixes both of your remarks. It has been made
against today's cvs snapshot.
> [Aside: Eew. I can't believe Tcl_Eval is still being used!]
Well... I'm not enough involved in insight's guts and tcl to share your
estonishment. You're probably right. But I can say at least this call is
clear enough to understand what's happening :-)
In fact I'm only the insight's packager for Fedora.
Thanks for your help.
Cheers,
Patrick
[-- Attachment #2: insight-7.4.50-sig2dead.patch --]
[-- Type: application/octet-stream, Size: 1362 bytes --]
diff -Naur src.orig/gdb/gdbtk/ChangeLog src.new/gdb/gdbtk/ChangeLog
--- src.orig/gdb/gdbtk/ChangeLog 2012-04-19 11:41:24.000000000 +0200
+++ src.new/gdb/gdbtk/ChangeLog 2012-04-19 17:04:04.601462401 +0200
@@ -1,3 +1,8 @@
+2012-04-19 Patrick Monnerat <pm@datasphere.ch>
+
+ * generic/gdbtk-hooks.c (gdbtk_annotate_signal): Avoid
+ dereferencing a null (i.e.: dead) process/thread.
+
2012-04-19 Roland Schwingel <roland.schwingel@onevision.com>
* generic/gdbtk-bp.c: Updated copyright.
diff -Naur src.orig/gdb/gdbtk/generic/gdbtk-hooks.c src.new/gdb/gdbtk/generic/gdbtk-hooks.c
--- src.orig/gdb/gdbtk/generic/gdbtk-hooks.c 2012-03-28 15:09:12.000000000 +0200
+++ src.new/gdb/gdbtk/generic/gdbtk-hooks.c 2012-04-19 16:57:27.929884730 +0200
@@ -804,7 +804,7 @@
gdbtk_annotate_signal (void)
{
char *buf;
- struct thread_info *tp = inferior_thread ();
+ struct thread_info *tp;
/* Inform gui that the target has stopped. This is
a necessary stop button evil. We don't want signal notification
@@ -812,6 +812,11 @@
timeout. */
Tcl_Eval (gdbtk_interp, "gdbtk_stop_idle_callback");
+ if (ptid_equal (inferior_ptid, null_ptid))
+ return;
+
+ tp = inferior_thread ();
+
buf = xstrprintf ("gdbtk_signal %s {%s}",
target_signal_to_name (tp->suspend.stop_signal),
target_signal_to_string (tp->suspend.stop_signal));
next prev parent reply other threads:[~2012-04-19 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 12:48 Patrick Monnerat
2012-04-19 0:22 ` Keith Seitz
2012-04-19 15:19 ` Patrick Monnerat [this message]
2012-04-19 16:59 ` Keith Seitz
2012-04-19 17:51 ` Patrick Monnerat
2012-04-19 19:50 ` Keith Seitz
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=AB5E58B87EB73C46A38073D8F459F113D9F89A@dataspheresrv01 \
--to=patrick.monnerat@datasphere.ch \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).