Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: [sparc-solaris] unexpected warning when starting program
Date: Mon, 12 Mar 2007 11:07:00 -0000	[thread overview]
Message-ID: <20070312110718.GB21646@caradoc.them.org> (raw)
In-Reply-To: <20070312051646.GI14401@adacore.com>

On Sun, Mar 11, 2007 at 10:16:46PM -0700, Joel Brobecker wrote:
> Basically, the reason for the warning is that GDB thinks that the
> inferior unloaded ld.so.1. The reason for that is that, during startup,
> GDB does not immediately have access to base address of the dynamic
> linker structs. I suspect that this is because our real inferior
> hasn't been forked yet, or maybe is in the process of being forked.
> I haven't had time to look further into this.

It's because you've forked, but the dynamic linker has not run yet.
This is code I added recently.  The first time, we get the name of the
dynamic linker from the contents of .interp.  Later, after it's run,
we get it from the inferior's link_map list.

Maybe a gdbarch hook to override the name of the default dynamic
linker?  That's really bizarre though.  Maybe the OpenSolaris sources
give some insight to how it came up with /lib/ld.so.1.


-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-03-12 11:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12  5:16 Joel Brobecker
2007-03-12 11:07 ` Daniel Jacobowitz [this message]
2007-03-12 17:17   ` Joel Brobecker
2007-03-20  8:39   ` Denis PILAT
2007-04-10 21:40     ` Daniel Jacobowitz
2007-04-17 14:51       ` Denis PILAT
2007-03-12 22:03 ` Eli Zaretskii
2007-03-12 22:09   ` Joel Brobecker
2007-04-10 21:35 ` Daniel Jacobowitz
2007-04-11  6:45   ` 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=20070312110718.GB21646@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb@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