From: Keith Seitz <keiths@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: insight@sourceware.org
Subject: Re: Get build error
Date: Thu, 02 Dec 2010 02:33:00 -0000 [thread overview]
Message-ID: <4CF7045A.6000000@redhat.com> (raw)
In-Reply-To: <AANLkTi=J9akx9pE1umD3RTu18nQct1DAEVWSFx=riuwz@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
On 12/01/2010 06:15 PM, Hui Zhu wrote:
> Ping.
Thank you for reminding me... I've committed the following patch to fix
this.
Keith
ChangeLog
2010-12-01 Keith Seitz <keiths@valrhona.uglyboxes.com>
* generic/gdbtk-hooks.c (gdbtk_annotate_signal): Update to reflect
recnet thread_info changes.
[-- Attachment #2: stop_signal-update.patch --]
[-- Type: text/plain, Size: 1130 bytes --]
Index: generic/gdbtk-hooks.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-hooks.c,v
retrieving revision 1.50
diff -u -p -r1.50 gdbtk-hooks.c
--- generic/gdbtk-hooks.c 2 Dec 2009 19:29:42 -0000 1.50
+++ generic/gdbtk-hooks.c 2 Dec 2010 02:33:04 -0000
@@ -1,7 +1,7 @@
/* Startup code for Insight.
- Copyright (C) 1994, 1995, 1996, 1997, 1998, 2000, 200, 2002, 2003, 2004, 2008
- Free Software Foundation, Inc.
+ Copyright (C) 1994, 1995, 1996, 1997, 1998, 2000, 200, 2002, 2003, 2004,
+ 2008, 2010 Free Software Foundation, Inc.
Written by Stu Grossman <grossman@cygnus.com> of Cygnus Support.
@@ -808,8 +808,8 @@ gdbtk_annotate_signal (void)
Tcl_Eval (gdbtk_interp, "gdbtk_stop_idle_callback");
buf = xstrprintf ("gdbtk_signal %s {%s}",
- target_signal_to_name (tp->stop_signal),
- target_signal_to_string (tp->stop_signal));
+ target_signal_to_name (tp->suspend.stop_signal),
+ target_signal_to_string (tp->suspend.stop_signal));
if (Tcl_Eval (gdbtk_interp, buf) != TCL_OK)
report_error ();
free(buf);
next prev parent reply other threads:[~2010-12-02 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 13:05 Hui Zhu
2010-12-02 2:15 ` Hui Zhu
2010-12-02 2:33 ` Keith Seitz [this message]
2010-12-02 8:25 ` Hui Zhu
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=4CF7045A.6000000@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=teawater@gmail.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).