From: "Dave Korn" <dk@artimi.com>
To: <gdb@sources.redhat.com>
Subject: RE: Debug a cross-compiled binary using GDB !!
Date: Wed, 14 Jul 2004 11:27:00 -0000 [thread overview]
Message-ID: <NUTMEGAhsFt4cwqqPxJ0000088a@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <20040714090214.49090.qmail@web90108.mail.scd.yahoo.com>
> -----Original Message-----
> From: gdb-owner On Behalf Of karthik bala guru
> Sent: 14 July 2004 10:02
> Hello,
> I have builded gcc, glibc and gdb as
^^^
> arm-targetted and i386-linux-hosted.
^^^^^^^^^^^^^
I see you found out the answer to your last two posts for yourself!
> In my humble opinion, gdb couldn't
> execute arm-targetted binary on i386
> machine and probably I need a arm simulator or arm
> board connected to PC.
Yes, you could use either a remote arm development board, or a software
simulator; gdb comes with a simulator built in.
> I think "target sim" has something to do with it. But
> I
> can't find any information about "target sim". Can
> anyone help me or advice me what to do?
Check the gdb texinfo files by doing "info gdb", then search for "target
sim". Basically you just say "target sim" instead of "target remote" or
"target exec", then use commands like load, run, break, continue etc. as
normal.
> Or Is it possible to cross debug a application
> from within a i386 machine.
It certainly ought to work. Note however that the simulator will have no
notion of i/o hardware or similar.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2004-07-14 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 11:12 karthik bala guru
2004-07-14 11:27 ` Dave Korn [this message]
2004-07-16 9:04 ` karthik bala guru
2004-07-16 9:04 ` Dave Korn
2004-07-14 12:22 ` (gdb) list Can't find a default source file murugesan
2004-07-14 15:04 ` Monika Chaddha
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=NUTMEGAhsFt4cwqqPxJ0000088a@NUTMEG.CAM.ARTIMI.COM \
--to=dk@artimi.com \
--cc=gdb@sources.redhat.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