public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Hinko Kocevar <hinko.kocevar@iskramedical.si>
Cc: Kris Warkentin <kewarken@qnx.com>, gdb@sources.redhat.com
Subject: Re: remote debugging and source files
Date: Wed, 25 Aug 2004 14:16:00 -0000	[thread overview]
Message-ID: <20040825141558.GA27216@nevyn.them.org> (raw)
In-Reply-To: <412C9AFC.70608@iskramedical.si>

On Wed, Aug 25, 2004 at 03:58:20PM +0200, Hinko Kocevar wrote:
> Kris Warkentin wrote:
> >Hmm...according to your info shared, you have the loader here:
> >
> >0x40001460  0x40011914  No 
> >/opt/arm-linux/gcc-3.3.3-glibc-2.3.2/arm-softfloat-linux-gnu/lib/ld-linux.so.2 
> >
> >
> >so the breakpoint doesn't seem entirely unreasonable.  Is there any 
> >possibility that you have a different ld-linux.so.2 on the host and 
> >target? 
> 
> It is same version on the host and on the target - glibc-2.3.2., but the 
> one on target is cross compiled for ARM architecture, though. Is there 
> any other kind of difference we are interested here?

No, the copy of glibc on the target and the copy in
/opt/arm-linux/gcc-3.3.3-glibc-2.3.2/arm-softfloat-linux-gnu.  Are they
identical builds?


-- 
Daniel Jacobowitz

  reply	other threads:[~2004-08-25 14:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 14:05 Hinko Kocevar
2004-08-24 15:34 ` Hinko Kocevar
2004-08-24 15:56   ` Hinko Kocevar
2004-08-24 16:35     ` Kris Warkentin
2004-08-24 17:42       ` Hinko Kocevar
2004-08-24 17:53         ` Daniel Jacobowitz
2004-08-24 18:05         ` Kris Warkentin
2004-08-25 13:58           ` Hinko Kocevar
2004-08-25 14:16             ` Daniel Jacobowitz [this message]
2004-08-25 14:30               ` Hinko Kocevar
2004-08-26 19:38                 ` remote debugging and source files - SOLVED Hinko Kocevar
2004-08-25 14:33             ` remote debugging and source files Kris Warkentin

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=20040825141558.GA27216@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=hinko.kocevar@iskramedical.si \
    --cc=kewarken@qnx.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).