public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: insight@sourceware.org
Subject: Branch tag gdb_7_5-branch added for insight specific sources
Date: Wed, 29 Aug 2012 22:24:00 -0000	[thread overview]
Message-ID: <20120829152411.208ae783@mesquite.lan> (raw)

I've added the gdb_7_5-branch branch tag for the following insight
specific source directories:

    gdb/gdbtk
    gdb/testsuite/gdb.gdbtk
    tcl
    tk
    itcl
    libgui

As usual, I found that I couldn't use the same date as that used by
GDB for creating the branch point.  Also, as usual, I didn't create
a branch point for insight, though I can do so if requested.  For
the insight specific sources, I used -D 2012-08-09 in order to
bring in Roland Schwingel's fixes to make insight compilable. 

I had to revert one of those changes, however, for the gdb 7.5 branch.
I'm appending this patch along with the ChangeLog entry below.  I've
committed this patch to the branch.

Kevin

2012-08-29  Kevin Buettner  <kevinb@redhat.com>

	* generic/gdbtk-cmds.c (gdb_load_info): Revert change
	regarding make_cleanup_bfd_unref for the gdb 7.5 branch.


Index: generic/gdbtk-cmds.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-cmds.c,v
retrieving revision 1.128
diff -u -p -r1.128 gdbtk-cmds.c
--- generic/gdbtk-cmds.c	8 Aug 2012 13:50:32 -0000	1.128
+++ generic/gdbtk-cmds.c	29 Aug 2012 22:07:37 -0000
@@ -968,7 +968,7 @@ gdb_load_info (ClientData clientData, Tc
       gdbtk_set_result (interp, "Open of %s failed", filename);
       return TCL_ERROR;
     }
-  old_cleanups = make_cleanup_bfd_unref (loadfile_bfd);
+  old_cleanups = make_cleanup_bfd_close (loadfile_bfd);
 
   if (!bfd_check_format (loadfile_bfd, bfd_object))
     {

                 reply	other threads:[~2012-08-29 22:24 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=20120829152411.208ae783@mesquite.lan \
    --to=kevinb@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).