Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: gdb@sources.redhat.com
Subject: Re: Troubleshooting broken gdbserver/remote-target
Date: Tue, 23 Jun 2009 18:11:00 -0000	[thread overview]
Message-ID: <h1r5sa$iho$1@ger.gmane.org> (raw)
In-Reply-To: <8ac60eac0906230959k7d89636av6edd36d8d25b7457@mail.gmail.com>

On 2009-06-23, Paul Pluzhnikov <ppluzhnikov@google.com> wrote:

>> What would cause gdb to miss out on the fact that
>> /lib/libuClibc-0.9.30.1.so is mapped?
>>
>> Where does gdb get mapping info?
>
> I believe the code GDB should be using on Linux is in solib-svr4.c
>
> Gdb looks for _r_debug symbol and DT_DEBUG Elf32_Dyn entry to
> find the 'struct r_debug', which contains a linked list of
> loaded shared libraries, and traverses that list.

Thanks for the hint.  When I have a chance I'll see if I can
figure out what's wrong.  I presume gdb is looking for those
symbols in the ELF executable file?

> My guess: either GDB is not finding _r_debug, or (more likely)
> is not traversing the list correctly.

I found other reports that 6.8 doesn't work for ARM targets,
but 6.7.1 does.  I switched from 6.8 to 6.7.1, and that fixed
the problem.

Now to see if that fixed the problems with thread support
as well...

-- 
Grant Edwards                   grante             Yow! I know things about
                                  at               TROY DONAHUE that can't
                               visi.com            even be PRINTED!!


  reply	other threads:[~2009-06-23 18:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  3:07 Grant Edwards
2009-06-23  5:09 ` Grant Edwards
2009-06-23 17:00   ` Paul Pluzhnikov
2009-06-23 18:11     ` Grant Edwards [this message]
2009-06-23 18:25       ` Grant Edwards
2009-06-24 19:49         ` Grant Edwards

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='h1r5sa$iho$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=gdb@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