Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Xu Haojun-a18535 <hjXu@motorola.com>
Cc: Michael Snyder <Michael.Snyder@palmsource.com>,
		gdb@sourceware.org, Xie ShaoHua-A22496 <A22496@motorola.com>
Subject: Re: Help with stepping into shared-library with strippedld-linuxon 	arm board
Date: Fri, 23 Mar 2007 13:16:00 -0000	[thread overview]
Message-ID: <20070323131609.GA31820@caradoc.them.org> (raw)
In-Reply-To: <6D989D7EEBF1A34EA5CAF6A24FD3E15801E3D088@zmy16exm63.ds.mot.com>

On Fri, Mar 23, 2007 at 09:10:56PM +0800, Xu Haojun-a18535 wrote:
> Daniel,
> 
> I know your solution and it works really.
> 
> But actually we are trying to figure out ways to debug an arm board with ld-linux.so stripped of all symbols. 
> "There are a lot of things that will go wrong without symbols." That's exactly what we want to make clear - how the symbols of ld-linux.so is used in gdb and where will go wrong without these symbols.
> So that we can figure out ways to serve our special reqs. 
> Any clue about this?

No.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-03-23 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 15:29 Help with stepping into shared-library with stripped ld-linux on " Xu Haojun-a18535
2007-03-22 15:45 ` Daniel Jacobowitz
     [not found]   ` <1174588974.9964.9.camel@localhost.localdomain>
     [not found]     ` <6D989D7EEBF1A34EA5CAF6A24FD3E15801E3D06D@zmy16exm63.ds.mot.com>
2007-03-23 11:55       ` Help with stepping into shared-library with stripped ld-linuxon " Daniel Jacobowitz
2007-03-23 13:12         ` Help with stepping into shared-library with strippedld-linuxon " Xu Haojun-a18535
2007-03-23 13:16           ` 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=20070323131609.GA31820@caradoc.them.org \
    --to=drow@false.org \
    --cc=A22496@motorola.com \
    --cc=Michael.Snyder@palmsource.com \
    --cc=gdb@sourceware.org \
    --cc=hjXu@motorola.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