Re: problem with cross-dev gdb

Re: problem with cross-dev gdb

[toon.diels]

Hello Daniel,

thank you for the tip. I have evaluated already a new snapshot but it turned out into thesame segmentation faults
I encountered with gdb5.0 (with several patches for MIPS support). The segmentation faults appear to be caused on the
host and not on the target. (when turning on debug remote before setting a breakpoint, no data transfers are visible to or from the target
, only a segmentation error on the host).

For my target I have build a mipsel-linux-toolchain based on a recent SGI-tarball: GCC3.0-GLIBC-2.2.3-BINUTILS2.11.90.
This toolchain is even newer then the one I am using on my host: GCC2.95.2-GLIBC-2.XX-BINUTILS2.10.91
Is it possible that the host-target toolchain difference (especially glibc) prevent gdb to operate correct in cross-dev mode?

I have already been debugging the native gdb built for target mipsel-linux with another host debugger without finding real pointers
to the problem. Do you have some debugging tips?

thank you and kind regards,

Toon Diels





Daniel Jacobowitz <drow@mvista.com>@sources.redhat.com on 10/09/2001 20:30:52

Sent by:  gdb-owner@sources.redhat.com


To:     Toon Diels/HAS/BE/PHILIPS@EMEA1
cc:     gdb@sourceware.cygnus.com
Subject:  Re: problem with cross-dev gdb
Classification:



On Mon, Sep 10, 2001 at 09:10:19PM +0200, toon.diels@philips.com wrote:
> Hello,
>
> I am porting Linux to a MIPS based embedded system. In order to get a decent cross-dev environment, I have
> cross-compiled gdb5.0 for a pc-linux host and a mipsel-linux target. I connect my gdbserver on target and gdb on the host via
> network link:
>
> target = 130.145.72.8
> host = 130.145.72.10
>
> target> gdbserver host:1234 myAppl
>
> host> mipsel-linux-gdb myAppl
> host>(gdb)target remote 130.145.72.8:1234
>
> When these components connect, I can only use the "continue" command. Other gdb commands as breakpoint, list etc result
> in segmentation faults. These segmentation faults are reported on the host via gdb. The target gdbserver indicates that it received
> : readchar : GOT EOF. Does anyone have a clue on what I am doing wrong?

You're using gdb 5.0 for MIPS/Linux :)  Don't Do That.  Grab a 5.1
snapshot instead; support for MIPS/Linux was not contributed until
recently.

> When using the gdbserver, do I still need the gdb-stubs
> in the target kernel?

No, you don't need a GDB stub unless you are using kgdb.

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

Re: problem with cross-dev gdb

[Daniel Jacobowitz]

On Mon, Sep 17, 2001 at 05:44:22PM +0200, toon.diels@philips.com wrote:
> Hello Daniel,
> 
> thank you for the tip. I have evaluated already a new snapshot but it turned out into thesame segmentation faults
> I encountered with gdb5.0 (with several patches for MIPS support). The segmentation faults appear to be caused on the
> host and not on the target. (when turning on debug remote before setting a breakpoint, no data transfers are visible to or from the target
> , only a segmentation error on the host).
> 
> For my target I have build a mipsel-linux-toolchain based on a recent SGI-tarball: GCC3.0-GLIBC-2.2.3-BINUTILS2.11.90.
> This toolchain is even newer then the one I am using on my host: GCC2.95.2-GLIBC-2.XX-BINUTILS2.10.91
> Is it possible that the host-target toolchain difference (especially glibc) prevent gdb to operate correct in cross-dev mode?
> 
> I have already been debugging the native gdb built for target mipsel-linux with another host debugger without finding real pointers
> to the problem. Do you have some debugging tips?

Not really.  It works perfectly well for me, using both serial and TCP
debugging.

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

problem with cross-dev gdb

[toon.diels]

Hello,

I am porting Linux to a MIPS based embedded system. In order to get a decent cross-dev environment, I have
cross-compiled gdb5.0 for a pc-linux host and a mipsel-linux target. I connect my gdbserver on target and gdb on the host via
network link:

target = 130.145.72.8
host = 130.145.72.10

target> gdbserver host:1234 myAppl

host> mipsel-linux-gdb myAppl
host>(gdb)target remote 130.145.72.8:1234

When these components connect, I can only use the "continue" command. Other gdb commands as breakpoint, list etc result
in segmentation faults. These segmentation faults are reported on the host via gdb. The target gdbserver indicates that it received
: readchar : GOT EOF. Does anyone have a clue on what I am doing wrong? When using the gdbserver, do I still need the gdb-stubs
in the target kernel?

Thanks,

toon

Re: problem with cross-dev gdb

[Daniel Jacobowitz]

On Mon, Sep 10, 2001 at 09:10:19PM +0200, toon.diels@philips.com wrote:
> Hello,
> 
> I am porting Linux to a MIPS based embedded system. In order to get a decent cross-dev environment, I have
> cross-compiled gdb5.0 for a pc-linux host and a mipsel-linux target. I connect my gdbserver on target and gdb on the host via
> network link:
> 
> target = 130.145.72.8
> host = 130.145.72.10
> 
> target> gdbserver host:1234 myAppl
> 
> host> mipsel-linux-gdb myAppl
> host>(gdb)target remote 130.145.72.8:1234
> 
> When these components connect, I can only use the "continue" command. Other gdb commands as breakpoint, list etc result
> in segmentation faults. These segmentation faults are reported on the host via gdb. The target gdbserver indicates that it received
> : readchar : GOT EOF. Does anyone have a clue on what I am doing wrong?

You're using gdb 5.0 for MIPS/Linux :)  Don't Do That.  Grab a 5.1
snapshot instead; support for MIPS/Linux was not contributed until
recently.

> When using the gdbserver, do I still need the gdb-stubs
> in the target kernel?

No, you don't need a GDB stub unless you are using kgdb.

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