Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: checked in: Re: RFC: solib.c:solib_map_sections so->so_name clobbering
Date: Thu, 11 Apr 2013 04:03:00 -0000	[thread overview]
Message-ID: <20130411012015.GF24389@adacore.com> (raw)
In-Reply-To: <20130328232724.GF4758@adacore.com>

> gdb/ChangeLog:
> 
>         * solib.c (solib_map_sections): Remove code overwriting
>         SO->SO_NAME with the bfd's filename.

Now checked in.

-- 
Joel


  parent reply	other threads:[~2013-04-11  1:20 UTC|newest]

Thread overview: 19+ 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         ` darwin: fix SO name in "info sharedlibrary" Tom Tromey
2013-04-11  5:40           ` checked in: " Joel Brobecker
2013-04-11  4:03       ` Joel Brobecker [this message]
2013-10-26  2:30 checked in: Re: RFC: solib.c:solib_map_sections so->so_name clobbering Luis Machado
2013-10-26  2:35 ` Luis Machado
2013-10-26  4:29   ` Joel Brobecker
2013-10-27  2:46     ` Luis Machado
2013-10-28 11:39       ` Joel Brobecker
2013-12-04 16:59         ` Joel Brobecker
2013-12-15 10:02           ` 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=20130411012015.GF24389@adacore.com \
    --to=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