Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: 'Daniel Jacobowitz' <drow@false.org>
To: xchen <xchen@sunrisetelecom.com.cn>
Cc: gdb@sourceware.org
Subject: Re: (Rising Spam Alert)Re: (Rising Spam Alert)Re: wrong lib address
Date: Mon, 03 Sep 2007 14:49:00 -0000	[thread overview]
Message-ID: <20070903144930.GA7463@caradoc.them.org> (raw)
In-Reply-To: <20070903103005.07EAD98109@nan.false.org>

On Mon, Sep 03, 2007 at 06:30:58PM +0800, xchen wrote:
>  
> Hi Daniel 
> 
> 	I have resolved this problem. I misunderstood the mean of
> solib-absolute-prefix. And now I use solib-search-path to load the library.
> Bad luck!  New errors occured include Malformed packet(b) (missing colon)
> and Invalid remote reply when I continue to debug my peogram. Belowed is the
> snapshot
> 
> (gdb) set solib-absolute-prefix /root/
> (gdb) set solib-search-path
> /opt/montavista/pro/devkit/ppc/8xx/target/lib/:/opt/montavista/pro/devkit/pp
> c/8xx/target/usr/lib/

No.  Don't use solib-search-path for this.

Use:
  set solib-absolute-prefix /opt/montavista/pro/devkit/ppc/8xx/target

> (gdb) n
> warning: Invalid remote reply: n8003

You are using MontaVista's gdbserver.  You should be using their GDB,
too.  This only works with both.


-- 
Daniel Jacobowitz
CodeSourcery


       reply	other threads:[~2007-09-03 14:49 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070903103005.07EAD98109@nan.false.org>
2007-09-03 14:49 ` 'Daniel Jacobowitz' [this message]
2007-09-04 10:46   ` (Rising Spam Alert)Re: " xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-04 10:46   ` xchen
2007-09-03 10:30 xchen
  -- strict thread matches above, loose matches on Subject: below --
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen
2007-09-03 10:30 xchen

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=20070903144930.GA7463@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=xchen@sunrisetelecom.com.cn \
    /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