From: Andrew Cagney <ac131313@redhat.com>
To: Paul Mundt <paul.mundt@timesys.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: Re: gdbserver on PowerPC Issues
Date: Wed, 20 Nov 2002 12:23:00 -0000 [thread overview]
Message-ID: <3DDBEF24.50607@redhat.com> (raw)
In-Reply-To: <1037820786.1317.33.camel@Origin>
> On Wed, 2002-11-20 at 14:21, Daniel Jacobowitz wrote:
>
>> Mind setting solib-absolute-prefix and stracing GDB to see what it was
>> opening, then? It really should work.
>
>
> My fault, I wasn't aware that solib-absolute-prefix appended /lib to the
> path. As a result, it was looking in lib/lib, which caused ENOENT.
No, its a bug in the doco :-( A better section on remote debugging is
needed.
Andrew
> By handing it the path with the /lib trimmed, everything works fine.
>
> Regards,
>
> -- Paul Mundt <paul.mundt@timesys.com> TimeSys Corporation
next prev parent reply other threads:[~2002-11-20 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 9:18 Paul Mundt
2002-11-20 10:39 ` Daniel Jacobowitz
2002-11-20 11:19 ` Paul Mundt
2002-11-20 11:21 ` Daniel Jacobowitz
2002-11-20 11:29 ` Paul Mundt
2002-11-20 12:23 ` Andrew Cagney [this message]
2002-11-20 11:29 ` Paul Koning
2002-11-20 11:45 ` 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=3DDBEF24.50607@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=paul.mundt@timesys.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