From: "John Zhou" <zjzhou@newrocktech.com>
To: <kotaeji@secui.com>, <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: [Q] question about using x86 gdb to debug the remote ppc target (kgdb)
Date: Fri, 9 Jan 2004 13:50:58 +0800 [thread overview]
Message-ID: <000801c3d674$8ed1f260$b702a8c0@newrock2> (raw)
In-Reply-To: <006701c3d673$30cb7890$2c373737@hwteam6549>
Maybe you should use ppc_82xx-gdb to connect remote target.
Regards,
John
-----Original Message-----
From: owner-linuxppc-embedded@lists.linuxppc.org
[mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of kotaeji
Sent: Friday, January 09, 2004 1:41 PM
To: linuxppc-embedded@lists.linuxppc.org
Subject: [Q] question about using x86 gdb to debug the remote ppc target
(kgdb)
Hi, I have a question about using kgdb on PowerPC (8245)
Is it possible that the host is x86, and the remote target
is powerpc as following picture ?
HOST(x86) ----------------------------- TARGET(ppc)
gdb serial line kgdb patch
When I connect to target by gdb on x86 and do "info registers"
to show target registers, it shows x86 registers.
(gdb) info registers
eax 0x2000 8192
ecx 0xc3c6dd00 -1010377472
edx 0xc3c6c000 -1010384896
ebx 0xc0341540 -1070328512
esp 0xc0341400 0xc0341400
ebp 0xc3c6dd80 0xc3c6dd80
esi 0xc3c6de4c -1010377140
edi 0x280008e8 671090920
eip 0x0 0x0
eflags 0x2 2
cs 0x0 0
ss 0xc5000000 -989855744
ds 0xfed2a80 267201152
es 0x10020300 268567296
fs 0x0 0
gs 0x0 0
Is there any way that I can use x86 gdb to debug remote ppc target?
Should I use powerpc gdb (like YellowDog) in order to debug
ppc target?
Any comments appreciated.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-09 5:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 5:41 [Q] question about using x86 gdb to debug the remote ppc target (kgdb) kotaeji
2004-01-09 5:50 ` John Zhou [this message]
2004-01-09 16:42 ` Christopher R. Johnson
2004-01-09 17:40 ` TLB and CSSBAR problems with MPC8540 and BDI2000 Fahd Abidi
2004-01-09 17:54 ` Dan Malek
2004-01-09 19:45 ` Matthew S. McClintock
2004-01-09 22:13 ` Dan Malek
2004-01-09 22:18 ` Matthew S. McClintock
2004-01-09 22:28 ` Dan Malek
2004-01-12 15:56 ` Dan Malek
2004-01-12 20:19 ` Matthew S. McClintock
2004-01-14 1:43 ` Dan Malek
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='000801c3d674$8ed1f260$b702a8c0@newrock2' \
--to=zjzhou@newrocktech.com \
--cc=kotaeji@secui.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 NNTP newsgroup(s).