From: Keith Seitz <keiths@redhat.com>
To: insight <insight@sourceware.org>
Subject: [PATCH] Fix build for recent symbol searching updates in gdb
Date: Thu, 15 Aug 2013 14:26:00 -0000 [thread overview]
Message-ID: <520CE51B.4010500@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 237 bytes --]
Hi,
I've committed the attached patch to do $SUBJECT. This should get the
build working again.
Keith
2013-08-15 Keith Seitz <keiths@redhat.com>
* generic/gdbtk-cmds.c (gdb_search): Update for symbol
searching API update in gdb.
[-- Attachment #2: build-updates.patch --]
[-- Type: text/x-patch, Size: 1363 bytes --]
Index: generic/gdbtk-cmds.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-cmds.c,v
retrieving revision 1.135
diff -u -p -r1.135 gdbtk-cmds.c
--- generic/gdbtk-cmds.c 30 Jul 2013 23:16:43 -0000 1.135
+++ generic/gdbtk-cmds.c 15 Aug 2013 14:19:47 -0000
@@ -1461,7 +1461,7 @@ gdb_search (ClientData clientData, Tcl_I
search_symbols (regexp, space, nfiles, files, &ss);
if (ss != NULL)
- old_chain = make_cleanup_free_search_symbols (ss);
+ old_chain = make_cleanup_free_search_symbols (&ss);
Tcl_SetListObj (result_ptr->obj_ptr, 0, NULL);
@@ -1477,16 +1477,16 @@ gdb_search (ClientData clientData, Tcl_I
if ((p->symbol != NULL
&& strncmp (SYMBOL_LINKAGE_NAME (p->symbol), "__tf", 4) != 0
&& strncmp (SYMBOL_LINKAGE_NAME (p->symbol), "_GLOBAL_", 8) != 0)
- || p->msymbol != NULL)
+ || p->msymbol.minsym != NULL)
{
elem = Tcl_NewListObj (0, NULL);
- if (p->msymbol == NULL)
+ if (p->msymbol.minsym == NULL)
Tcl_ListObjAppendElement (interp, elem,
Tcl_NewStringObj (SYMBOL_PRINT_NAME (p->symbol), -1));
else
Tcl_ListObjAppendElement (interp, elem,
- Tcl_NewStringObj (SYMBOL_PRINT_NAME (p->msymbol), -1));
+ Tcl_NewStringObj (SYMBOL_PRINT_NAME (p->msymbol.minsym), -1));
if (show_files)
{
reply other threads:[~2013-08-15 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=520CE51B.4010500@redhat.com \
--to=keiths@redhat.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).