From: Daniel Jacobowitz <drow@false.org>
To: philippe.vivarelli@mindspeed.com
Cc: gdb@sources.redhat.com
Subject: Re: Remote debugging using gdbserver with threads on ARM linux: No backtrace
Date: Tue, 12 Oct 2004 19:48:00 -0000 [thread overview]
Message-ID: <20041012134250.GA676@nevyn.them.org> (raw)
In-Reply-To: <OF42C0C642.11E54386-ONC1256F2B.0028F222@nice.mindspeed.com>
On Tue, Oct 12, 2004 at 09:34:10AM +0200, philippe.vivarelli@mindspeed.com wrote:
> The .gdbinit file configured as follow:
> hand SIG32 nostop
> set complaints 1
> set confirm 1
> set solib-absolute-prefix /dev/null
> set solib-search-path /usr/local/arm-tools/arm-linux/lib/
No, that's wrong. Remove the "hand SIG32 nostop". Remove the
solib-search-path. Set solib-absolute-prefix to
/usr/local/arm-tools/arm-linux. See if that works better.
Are you sure the libraries in that directory are both unstripped and
otherwise exactly the same as the ones on your target?
If you don't use solib-absolute-prefix, we may not find the dynamic
linker, so thread breakpoints will not be set properly.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-10-12 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 15:56 philippe.vivarelli
2004-10-12 19:48 ` Daniel Jacobowitz [this message]
2004-10-13 0:31 philippe.vivarelli
2004-10-13 4:57 ` Daniel Jacobowitz
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=20041012134250.GA676@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=philippe.vivarelli@mindspeed.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