Debugging an Arm Evaluator7T using Gdb

Debugging an Arm Evaluator7T using Gdb

[Pierre Habraken]

Hello,

I am not sure that this list is the right one, but I did find another
one where to post my question...

I am looking instructions or informations about how to cross-debug an
Arm target using RDI and ADP using gdb 5.2 on a Linux host.
The file README.CYGNUS in the rdi-share directory tells the reader to
have a look at the book "ARM's Software Development Tools Reference
Manual" (Remote Debugging chapter) but I did not find this reference on
the Arm site.

Uploading a program to the target looks to be working fine.
Setting a breakpoint too.
But after that, running the program makes gdb display a warning message
and then hang :
======================================================================
(gdb) target rdi /dev/ttyS1
Angel Debug Monitor V1.32 (ARM Ltd unreleased) for Evaluator7T, IRQ
Built Nov 19 2001
Serial Rate:   9600
RDI_info: internal error, unimplemented message
Connected to ARM RDI target.
(gdb) load
Loading section .text, size 0x9b78 lma 0x8000
Loading section SWI_AREA, size 0x78 lma 0x11b78
Loading section STARTUP_AREA, size 0x34 lma 0x11bf0
Loading section .rodata, size 0x468 lma 0x11c24
Loading section .data, size 0x85c lma 0x1218c
Loading section .eh_frame, size 0x4 lma 0x129e8
Loading section .ctors, size 0x8 lma 0x129ec
Loading section .dtors, size 0x8 lma 0x129f4
Start address 0x8000, load size 43260
Transfer rate: 6292 bits/sec, 475 bytes/write.
(gdb) break main
Breakpoint 1 at 0x8564: file noyau.c, line 407.
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y

<gdb hangs here, I have to kill it from a shell>
======================================================================

I am very far from being a Gdb expert, and also I am a newbie in
debugging an Arm target. So I would really appreciate any kind of
help !... 

Pierre
-- 
________________________________________________________________________
Pierre HABRAKEN - mailto:Pierre.Habraken@imag.fr
Tél: 04 76 82 72 83 - Fax: 04 76 82 72 87
IMAG-LSR BP72 38402 SAINT MARTIN D'HERES Cedex
________________________________________________________________________

Re: Debugging an Arm Evaluator7T using Gdb

[Daniel Jacobowitz]

On Sun, May 19, 2002 at 06:44:31PM +0200, Pierre Habraken wrote:
> Hello,
> 
> I am not sure that this list is the right one, but I did find another
> one where to post my question...
> 
> I am looking instructions or informations about how to cross-debug an
> Arm target using RDI and ADP using gdb 5.2 on a Linux host.
> The file README.CYGNUS in the rdi-share directory tells the reader to
> have a look at the book "ARM's Software Development Tools Reference
> Manual" (Remote Debugging chapter) but I did not find this reference on
> the Arm site.
> 
> Uploading a program to the target looks to be working fine.
> Setting a breakpoint too.
> But after that, running the program makes gdb display a warning message
> and then hang :
> ======================================================================
> (gdb) target rdi /dev/ttyS1
> Angel Debug Monitor V1.32 (ARM Ltd unreleased) for Evaluator7T, IRQ
> Built Nov 19 2001
> Serial Rate:   9600
> RDI_info: internal error, unimplemented message
> Connected to ARM RDI target.
> (gdb) load
> Loading section .text, size 0x9b78 lma 0x8000
> Loading section SWI_AREA, size 0x78 lma 0x11b78
> Loading section STARTUP_AREA, size 0x34 lma 0x11bf0
> Loading section .rodata, size 0x468 lma 0x11c24
> Loading section .data, size 0x85c lma 0x1218c
> Loading section .eh_frame, size 0x4 lma 0x129e8
> Loading section .ctors, size 0x8 lma 0x129ec
> Loading section .dtors, size 0x8 lma 0x129f4
> Start address 0x8000, load size 43260
> Transfer rate: 6292 bits/sec, 475 bytes/write.
> (gdb) break main
> Breakpoint 1 at 0x8564: file noyau.c, line 407.
> (gdb) run
> The program being debugged has been started already.
> Start it from the beginning? (y or n) y
> 
> <gdb hangs here, I have to kill it from a shell>

Try "continue" instead?


> ======================================================================
> 
> I am very far from being a Gdb expert, and also I am a newbie in
> debugging an Arm target. So I would really appreciate any kind of
> help !... 
> 
> Pierre
> -- 
> ________________________________________________________________________
> Pierre HABRAKEN - mailto:Pierre.Habraken@imag.fr
> Tél: 04 76 82 72 83 - Fax: 04 76 82 72 87
> IMAG-LSR BP72 38402 SAINT MARTIN D'HERES Cedex
> ________________________________________________________________________

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

Re: Debugging an Arm Evaluator7T using Gdb

[Pierre Habraken]

Daniel Jacobowitz wrote:
> [...]
> > Uploading a program to the target looks to be working fine.
> > Setting a breakpoint too.
> > But after that, running the program makes gdb display a warning message
> > and then hang :
> 
> Try "continue" instead?

Thanks to Daniel Jacobowitz and William A. Gatliff.

It works perfectly when typing "continue" right after having uploaded
the program to the board.

BTW, I do not understand why one have to type "run" for some targets
(e.g. sim) and "continue" for other ones (e.g. rdi) in order to trigger
program execution...

Pierre
-- 
________________________________________________________________________
Pierre HABRAKEN - mailto:Pierre.Habraken@imag.fr
Tél: 04 76 82 72 83 - Fax: 04 76 82 72 87
IMAG-LSR BP72 38402 SAINT MARTIN D'HERES Cedex
________________________________________________________________________

Re: Debugging an Arm Evaluator7T using Gdb

[William A. Gatliff]

Pierre:


On Mon, May 20, 2002 at 05:54:41PM +0200, Pierre Habraken wrote:
> BTW, I do not understand why one have to type "run" for some targets
> (e.g. sim) and "continue" for other ones (e.g. rdi) in order to trigger
> program execution...

Philosophically, it's because according to gdb, the remote inferior
process already has an identity, and all you're doing is connecting to
it and then continuing on; when you "run" something, gdb creates a new
inferior process from scratch.

... or something like that.  :^)


b.g.

> 
> Pierre
> -- 
> ________________________________________________________________________
> Pierre HABRAKEN - mailto:Pierre.Habraken@imag.fr
> Tél: 04 76 82 72 83 - Fax: 04 76 82 72 87
> IMAG-LSR BP72 38402 SAINT MARTIN D'HERES Cedex
> ________________________________________________________________________
> 

-- 
Bill Gatliff
bgat@billgatliff.com