Remote Debugging on an ARM target

Remote Debugging on an ARM target

[Frederic Kwiatkowski]

Hello all

I'm currently trying to debug an application that run on an ARM9 (with
Linux) target with gdb 6.3
So i've built gdbserver to run on the arm-linux.
Next i've built gdb for my host (i386-linux)

 The problem is that I've got something strange on my host once i'm
connected to the target:

[root@srv bin]# ./i386-linux-gdb /home/frk/essai_gdb/essai_gdb
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
 There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=i386-linux"...
(gdb) target remote  192.168.0.228:2345
Remote debugging using 192.168.0.228:2345
0x00000000 in ?? ()
(gdb) break main
Breakpoint 1 at 0x84c0: file essai_gdb.c, line 4.
(gdb) continue
Continuing.
Warning:
Cannot insert breakpoint -2.
Error accessing memory address 0xdaca: Erreur d'entrée/sortie.


0x00000000 in ?? () <<<<< this one is a little intrigant
and the "Cannot insert breakpoint -2.
 Error accessing memory address 0xdaca: Erreur d'entrée/sortie." too




The source code of the gdb_try is the following:
#include <stdio.h>

main ()
{
int num1, num2, total ;
printf("Enter first number : ");
scanf("%d", &num1);
printf("Enter second number : ");
scanf("%d", &num2);
total = num1 + num2;
printf("\nThe sum is : %d\n", total);
}



Does anyone have an idea about the origin of this problem?

With regards

Re: Remote Debugging on an ARM target

[Daniel Jacobowitz]

On Tue, Feb 07, 2006 at 03:44:47PM +0100, Frederic Kwiatkowski wrote:
> This GDB was configured as "--host=i686-pc-linux-gnu --target=i386-linux"...

No, your GDB must have --target=arm-linux to talk to an arm-linux
gdbserver.

-- 
Daniel Jacobowitz
CodeSourcery

Re: Remote Debugging on an ARM target

[Frederic Kwiatkowski]

thanks, but i've tryed it already and the make step was unsuccesful

../../../sim/arm/iwmmxt.c
../../../sim/arm/iwmmxt.c: In function 'WMAC':
../../../sim/arm/iwmmxt.c:2117: erreur: membre gauche de l'affectation invalide
../../../sim/arm/iwmmxt.c:2133: erreur: membre gauche de l'affectation invalide
../../../sim/arm/iwmmxt.c: In function 'WMADD':
../../../sim/arm/iwmmxt.c:2169: erreur: membre gauche de l'affectation invalide
../../../sim/arm/iwmmxt.c:2177: erreur: membre gauche de l'affectation invalide
../../../sim/arm/iwmmxt.c:2186: erreur: membre gauche de l'affectation invalide
../../../sim/arm/iwmmxt.c:2191: erreur: membre gauche de l'affectation invalide
../../../sim/arm/iwmmxt.c: In function 'WSLL':
../../../sim/arm/iwmmxt.c:2840: attention : integer constant is too
large for 'long' type
../../../sim/arm/iwmmxt.c: In function 'WSRA':
../../../sim/arm/iwmmxt.c:2917: attention : integer constant is too
large for 'long' type
../../../sim/arm/iwmmxt.c:2917: attention : integer constant is too
large for 'long' type
../../../sim/arm/iwmmxt.c:2919: attention : integer constant is too
large for 'long' type
../../../sim/arm/iwmmxt.c: In function 'WSRL':
../../../sim/arm/iwmmxt.c:2988: attention : integer constant is too
large for 'long' type
../../../sim/arm/iwmmxt.c: In function 'WUNPCKEH':
../../../sim/arm/iwmmxt.c:3290: attention : integer constant is too
large for 'long' type
../../../sim/arm/iwmmxt.c: In function 'WUNPCKEL':
../../../sim/arm/iwmmxt.c:3357: attention : integer constant is too
large for 'long' type
../../../sim/arm/iwmmxt.c: In function 'Fetch_Iwmmxt_Register':
../../../sim/arm/iwmmxt.c:3707: attention : incompatible implicit
declaration of built-in function 'memcpy'
../../../sim/arm/iwmmxt.c:3712: attention : incompatible implicit
declaration of built-in function 'memcpy'
../../../sim/arm/iwmmxt.c: In function 'Store_Iwmmxt_Register':
../../../sim/arm/iwmmxt.c:3722: attention : incompatible implicit
declaration of built-in function 'memcpy'
../../../sim/arm/iwmmxt.c:3727: attention : incompatible implicit
declaration of built-in function 'memcpy'
make[2]: *** [iwmmxt.o] Erreur 1
make[2]: Leaving directory `/home/smb/build/gdb-6.3/build-gdb/sim/arm'
make[1]: *** [all] Erreur 2
make[1]: Leaving directory `/home/smb/build/gdb-6.3/build-gdb/sim'
make: *** [all-sim] Erreur 2


and i was using the following command line:
../configure --target=arm-linux --prefix=/home/smb/build/gdb-
6.3/build-gdb/tools
2006/2/7, Daniel Jacobowitz <drow@false.org>:
> On Tue, Feb 07, 2006 at 03:44:47PM +0100, Frederic Kwiatkowski wrote:
> > This GDB was configured as "--host=i686-pc-linux-gnu --target=i386-linux"...
>
> No, your GDB must have --target=arm-linux to talk to an arm-linux
> gdbserver.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>

Re: Remote Debugging on an ARM target

[Daniel Jacobowitz]

On Tue, Feb 07, 2006 at 04:06:30PM +0100, Frederic Kwiatkowski wrote:
> thanks, but i've tryed it already and the make step was unsuccesful

Use a newer version of GDB or an older version of GCC.


-- 
Daniel Jacobowitz
CodeSourcery

Re: Remote Debugging on an ARM target

[Frederic Kwiatkowski]

thanks for all, it seems to run

now i'll try to use gdb

with kinds of regards


2006/2/7, Daniel Jacobowitz <drow@false.org>:
> On Tue, Feb 07, 2006 at 04:06:30PM +0100, Frederic Kwiatkowski wrote:
> > thanks, but i've tryed it already and the make step was unsuccesful
>
> Use a newer version of GDB or an older version of GCC.
>
>
> --
> Daniel Jacobowitz
> CodeSourcery
>

Re: Remote Debugging on an ARM target

[Frederic Kwiatkowski]

I've got one last question

Using GDB, i've got now a valid address but "??" appear:
0x40000a70 in ?? ()

what is the meaning of these?


2006/2/7, Frederic Kwiatkowski <stagedrt@gmail.com>:
> thanks for all, it seems to run
>
> now i'll try to use gdb
>
> with kinds of regards
>
>
> 2006/2/7, Daniel Jacobowitz <drow@false.org>:
> > On Tue, Feb 07, 2006 at 04:06:30PM +0100, Frederic Kwiatkowski wrote:
> > > thanks, but i've tryed it already and the make step was unsuccesful
> >
> > Use a newer version of GDB or an older version of GCC.
> >
> >
> > --
> > Daniel Jacobowitz
> > CodeSourcery
> >
>

Re: Remote Debugging on an ARM target

[Daniel Jacobowitz]

On Tue, Feb 07, 2006 at 05:06:06PM +0100, Frederic Kwiatkowski wrote:
> I've got one last question
> 
> Using GDB, i've got now a valid address but "??" appear:
> 0x40000a70 in ?? ()
> 
> what is the meaning of these?

It means that GDB doesn't have symbol information for that code
address (not surprising, that's probably in the dynamic linker before
your program starts running).

-- 
Daniel Jacobowitz
CodeSourcery

Re: Remote Debugging on an ARM target

[Frederic Kwiatkowski]

So i've got to specify a "--static" like option in my arm-linux-gcc to
be in static mode

i'll check that

thanks for all

2006/2/7, Daniel Jacobowitz <drow@false.org>:
> On Tue, Feb 07, 2006 at 05:06:06PM +0100, Frederic Kwiatkowski wrote:
> > I've got one last question
> >
> > Using GDB, i've got now a valid address but "??" appear:
> > 0x40000a70 in ?? ()
> >
> > what is the meaning of these?
>
> It means that GDB doesn't have symbol information for that code
> address (not surprising, that's probably in the dynamic linker before
> your program starts running).
>
> --
> Daniel Jacobowitz
> CodeSourcery
>