RE: insight/170: Assembly windows display .long 0 for remote targets

["Haji, Faizal \[Cont\]" <Faizal dot Haji at gdcanada dot com>]

The following reply was made to PR insight/170; it has been noted by GNATS.

From: "Haji, Faizal [Cont]" <Faizal.Haji@gdcanada.com>
To: "'kseitz@sources.redhat.com'" <kseitz@sources.redhat.com>, 
	"Haji, Faizal [Cont]" <Faizal.Haji@gdcanada.com>, 
	"'insight-prs@sources.redhat.com'" <insight-prs@sources.redhat.com>, 
	"'kseitz@sources.redhat.com'" <kseitz@sources.redhat.com>, 
	"'nobody@sources.redhat.com'" <nobody@sources.redhat.com>, 
	"'insight-gnats@sources.redhat.com'" <insight-gnats@sources.redhat.com>
Cc:  
Subject: RE: insight/170: Assembly windows display .long 0 for remote targ
	ets
Date: Thu, 29 Aug 2002 12:43:04 -0600

 >$ 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.
 
 No. The correct disassembly is displayed.
 
 BTW, our executable is built such that the code exists in ROM but gets
 copied over to RAM on bootup. The symbols in the ELF file point to the code
 in RAM and NOT ROM. There is no executable code in the RAM region within the
 ELF file.
 
 I think there should be a mode within Insight to read instructions from
 target and not the executable file.
 
 This problem is not a priority for us since the developers are using the
 non-GUI version of GDB under Emacs (I guess you can't teach old dogs new
 tricks).
 
 -----Original Message-----
 From: kseitz@sources.redhat.com [mailto:kseitz@sources.redhat.com]
 Sent: Wednesday, August 28, 2002 6:11 PM
 To: faizal.haji@gdcanada.com; insight-prs@sources.redhat.com;
 kseitz@sources.redhat.com; nobody@sources.redhat.com
 Subject: Re: insight/170: Assembly windows display .long 0 for remote
 targets
 
 
 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&databas
 e=insight&pr=170