From: Vladimir Prus <vladimir@codesourcery.com>
To: "Doug Evans" <dje@google.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Handle solaris dynamic linker name change.
Date: Thu, 27 Dec 2007 18:37:00 -0000 [thread overview]
Message-ID: <200712272118.29967.vladimir@codesourcery.com> (raw)
In-Reply-To: <e394668d0712271010k7161dda1x1bd7311241db2dbf@mail.gmail.com>
On Thursday 27 December 2007 21:10:31 Doug Evans wrote:
> On Dec 24, 2007 9:48 AM, Vladimir Prus <vladimir@codesourcery.com> wrote:
> > + /* On Solaris, when starting inferior we think that
> > + dynamic linker is /usr/lib/ld.so.1, but later on,
> > + the table of loaded shared libraries contains
> > + /lib/ld.so.1.
> > + Sometimes one file is a link to another, but sometimes
> > + they have identical content, but are not linked to each
> > + other. */
> > + if (strcmp (gdb->so_original_name, "/usr/lib/ld.so.1") == 0
> > + && strcmp (inferior->so_original_name, "/lib/ld.so.1") == 0)
> > + return 1;
>
> Do we want to support "ld --dynamic-linker /my/ld.so.1" here (i.e.
> user has specified a different ld.so), or if this happens is the bug
> avoided?
I would have expected the above to work -- as then gdb will think
dynamic linker is /my/ld.so.1 from the start, and it's not going
to change to anything else.
From previous discussion it's not clear why the name changes on
Solaris, but it appears the initial name is grabbed from ELF directly,
and will be /my/ld.so.1 in your case.
- Volodya
next prev parent reply other threads:[~2007-12-27 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 6:00 Vladimir Prus
2007-12-27 18:18 ` Doug Evans
2007-12-27 18:37 ` Vladimir Prus [this message]
2008-01-04 5:50 ` Joel Brobecker
2008-01-04 12:46 ` Daniel Jacobowitz
2008-01-04 15:30 ` Joel Brobecker
2008-01-07 15:24 ` Vladimir Prus
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=200712272118.29967.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sources.redhat.com \
/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