From: Matt Rice <ratmice@gmail.com>
To: "Amker.Cheng" <amker.cheng@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: cross debug glibc loader problem
Date: Wed, 10 Feb 2010 19:45:00 -0000 [thread overview]
Message-ID: <8ba6bed41002101145l3a29389cod7e3890b7e9a3312@mail.gmail.com> (raw)
In-Reply-To: <e8b251c81002100409q49e0fa91jcf7d9273166b7d7e@mail.gmail.com>
On Wed, Feb 10, 2010 at 4:09 AM, Amker.Cheng <amker.cheng@gmail.com> wrote:
> Hi all:
> I am trying to debug glibc loader, e.g. ld.so.
> I am following instructions at
> http://sources.redhat.com/glibc/wiki/Debugging/Loader_Debugging,
> the only difference is the cross debugging by running gdbserver from a
> mips simulator.
> the start up command is :
> ------------------------------
> EGLIBC=/home/user/working-dir/eglibc-test/build/glibc
> mipsel-linux-gnu-gdbserver --debug 192.168.10.2:3333 \
> $EGLIBC/elf/ld.so.1
> "--library-path
> $EGLIBC:\
> $EGLIBC/math:\
> $EGLIBC/elf:\
> $EGLIBC/dlfcn:\
> $EGLIBC/nss:\
> $EGLIBC/nis:\
> $EGLIBC/rt:\
> $EGLIBC/resolv:\
> $EGLIBC/crypt:\
> $EGLIBC/nptl \
> $EGLIBC/string/tester
>
> then I trying to connect gdbserver in gdb command line by :
>
> target remote 192.168.10.2:3333
>
> strangely, gdb complains that it :"Cannot access memory at address 0x32a14".
>
> I have totally no idea about this question, so please help and any
> tips will be appreciated.
>
> Thanks very much.
>
> the remote log file is attached, hoping helpful:
I would try it out with gdb from cvs, and if that doesn't work
investigate Jan Kratochvil's recent PIE: series of threads on the
gdb-patches list (at least some of which have been integrated), as I
am lead to believe from the first thread in the series that those
patches covered debugging ld.so.
next prev parent reply other threads:[~2010-02-10 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 12:09 Amker.Cheng
2010-02-10 19:45 ` Matt Rice [this message]
2010-02-11 3:12 ` Amker.Cheng
2010-02-11 20:59 ` Matt Rice
2010-02-11 22:02 ` Jan Kratochvil
2010-02-21 9:48 ` Amker.Cheng
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=8ba6bed41002101145l3a29389cod7e3890b7e9a3312@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=amker.cheng@gmail.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