From: Daniel Jacobowitz <drow@false.org>
To: Frank Meerkoetter <frank@betaversion.net>
Cc: gdb@sources.redhat.com
Subject: Re: Remote debugging and dynamic libraries
Date: Mon, 07 Nov 2005 00:12:00 -0000 [thread overview]
Message-ID: <20051107001221.GE19200@nevyn.them.org> (raw)
In-Reply-To: <436676B4.9030603@betaversion.net>
On Mon, Oct 31, 2005 at 08:55:32PM +0100, Frank Meerkoetter wrote:
> I gave it a try using "file test" and
> "set solib-absolute-prefix /usr/local/arm/arm-linux/" but had no success
> so far.
>
> frank@linux:~/uclibc_kram/apdf> arm-linux-gdb
This is the first time I recall seeing that you were using uclibc.
It's likely that shared library and thread debugging are simply broken
in your C library; you may want to ask the uclibc developers if they
expect it to work.
> (gdb) b 1
> Breakpoint 1 at 0x8428: file main.c, line 1.
> (gdb) c
> Continuing.
>
> Breakpoint 1, main () at main.c:1
> 1 int main() {
"info shared" at this point?
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-11-07 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 8:56 frank
[not found] ` <20051027143943.GA23938@nevyn.them.org>
2005-10-27 14:41 ` Daniel Jacobowitz
2005-10-31 19:55 ` Frank Meerkoetter
2005-11-07 0:12 ` Daniel Jacobowitz [this message]
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=20051107001221.GE19200@nevyn.them.org \
--to=drow@false.org \
--cc=frank@betaversion.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).