From: Keith Seitz <keiths@redhat.com>
To: insight <insight@sourceware.org>
Subject: [PATCH] Fix build error/struct bp_location->source_file
Date: Sat, 16 Feb 2013 07:07:00 -0000 [thread overview]
Message-ID: <511F300B.7040607@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
Hi,
This patch fixes the build problem reported earlier by Robert Bu.
If there are any further issues, please let me know.
Keith
2013-02-15 Keith Seitz <keiths@redhat.com>
* generic/gdbtk-bp.c (gdb_find_bp_at_line): Update struct
bp_location changes wrt source_file from GDB.
[-- Attachment #2: source_file.patch --]
[-- Type: text/x-patch, Size: 986 bytes --]
Index: generic/gdbtk-bp.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-bp.c,v
retrieving revision 1.50
diff -u -p -r1.50 gdbtk-bp.c
--- generic/gdbtk-bp.c 10 Nov 2012 18:09:30 -0000 1.50
+++ generic/gdbtk-bp.c 16 Feb 2013 07:05:15 -0000
@@ -1,5 +1,5 @@
/* Tcl/Tk command definitions for Insight - Breakpoints.
- Copyright (C) 2001-2012 Free Software Foundation, Inc.
+ Copyright (C) 2001-2013 Free Software Foundation, Inc.
This file is part of GDB.
@@ -249,8 +249,8 @@ gdb_find_bp_at_line (ClientData clientDa
Tcl_SetListObj (result_ptr->obj_ptr, 0, NULL);
ALL_BREAKPOINTS (b)
{
- if (b->loc && b->loc->line_number == line
- && !strcmp (b->loc->source_file, s->filename))
+ if (b->loc && b->loc->symtab && b->loc->line_number == line
+ && !strcmp (b->loc->symtab->filename, s->filename))
{
Tcl_ListObjAppendElement (NULL, result_ptr->obj_ptr,
Tcl_NewIntObj (b->number));
reply other threads:[~2013-02-16 7:07 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=511F300B.7040607@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).