From: Paul Koning <pkoning@equallogic.com>
To: drow@mvista.com
Cc: paul.mundt@timesys.com, gdb@sources.redhat.com
Subject: Re: gdbserver on PowerPC Issues
Date: Wed, 20 Nov 2002 11:29:00 -0000 [thread overview]
Message-ID: <15835.58034.655312.738765@pkoning.dev.equallogic.com> (raw)
In-Reply-To: <20021120192125.GA14049@nevyn.them.org>
>>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
Daniel> On Wed, Nov 20, 2002 at 02:22:56PM -0500, Paul Mundt wrote:
>> On Wed, 2002-11-20 at 13:39, Daniel Jacobowitz wrote: > The
>> problem is presumably that you haven't told GDB where to look for
>> > the dynamic linker and shared libraries. Try using 'set >
>> solib-absolute-prefix' before you 'target remote'.
>> >
>> Ah! This was indeed the problem. Though oddly enough, adjusting
>> solib-absolute-prefix didn't make the problem go away. I had to
>> set it to /dev/null and then set solib-search-patch to the proper
>> directory before the issue would fix itself.
>>
>> There was some CRIS documentation hinting that that would only be
>> necessary if the end of the path wasn't /lib, but in this case it
>> was.
Daniel> Mind setting solib-absolute-prefix and stracing GDB to see
Daniel> what it was opening, then? It really should work.
Depends on whether the library names are given in the image with a
leading slash or not. If yes, then the absolute prefix setting
matters; if not, the search path.
paul
next prev parent reply other threads:[~2002-11-20 19:29 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
2002-11-20 11:29 ` Paul Koning [this message]
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=15835.58034.655312.738765@pkoning.dev.equallogic.com \
--to=pkoning@equallogic.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