This is the mail archive of the
insight-prs@sources.redhat.com
mailing list for the Insight project.
Re: insight/170: Assembly windows display .long 0 for remote targets
- From: kseitz at sources dot redhat dot com
- To: faizal dot haji at gdcanada dot com, insight-prs at sources dot redhat dot com, kseitz at sources dot redhat dot com, nobody at sources dot redhat dot com
- Date: 29 Aug 2002 00:11:22 -0000
- Subject: Re: insight/170: Assembly windows display .long 0 for remote targets
- Reply-to: kseitz at sources dot redhat dot com, faizal dot haji at gdcanada dot com, insight-prs at sources dot redhat dot com, kseitz at sources dot redhat dot com, nobody at sources dot redhat dot com, insight-gnats at sources dot redhat dot com
Synopsis: Assembly windows display .long 0 for remote targets
Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Wed Aug 28 17:11:22 2002
Responsible-Changed-Why:
mine
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Wed Aug 28 17:11:22 2002
State-Changed-Why:
There could be any number of problems here.
The command line/console window use different mechanisms to do the disassembly: the Source Window reads instructions from the executable file, while the console will read from the target. What happens if you do:
$ powerpc-eabi-gdb -nw -nx -q foo.elf
(gdb) disassemble DeleteChar
Does it also show ".long 0x0"? If not, I'll need a testcase from you.
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=170