Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: darwin: fix SO name in "info sharedlibrary"
Date: Tue, 09 Apr 2013 02:17:00 -0000	[thread overview]
Message-ID: <87sj30ucvv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20130329015304.GJ4758@adacore.com> (Joel Brobecker's message of	"Thu, 28 Mar 2013 18:53:04 -0700")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> Here is the patch.

Joel> gdb/ChangeLog:

Joel>         * solib-darwin.c (darwin_bfd_open): Set the filename of the
Joel>         returned bfd to a copy of PATHNAME.

Joel> Tested on x86_64-darwin, no regression. Does it look OK for the branch?

Looks good to me.

Tom


  reply	other threads:[~2013-04-08 17:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 19:34 [PATCH 02/10] clean up allocation of bfd filenames Tom Tromey
2012-07-19 18:52 ` Jan Kratochvil
2012-07-19 20:59   ` Tom Tromey
2012-07-20 16:30     ` Tom Tromey
2012-07-20 18:07       ` Jan Kratochvil
2013-03-28 12:29 ` RFC: solib.c:solib_map_sections so->so_name clobbering (was: [PATCH 02/10] clean up allocation of bfd filenames) Joel Brobecker
2013-03-28 19:12   ` RFC: solib.c:solib_map_sections so->so_name clobbering Tom Tromey
2013-03-29  1:59     ` Joel Brobecker
2013-03-29  7:43       ` darwin: fix SO name in "info sharedlibrary" (was: "RFC: solib.c:solib_map_sections so->so_name clobbering") Joel Brobecker
2013-04-09  2:17         ` Tom Tromey [this message]
2013-04-11  5:40           ` checked in: darwin: fix SO name in "info sharedlibrary" Joel Brobecker
2013-04-11  4:03       ` checked in: Re: RFC: solib.c:solib_map_sections so->so_name clobbering Joel Brobecker

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=87sj30ucvv.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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