Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: toon.diels@philips.com
Cc: gdb@sourceware.cygnus.com
Subject: Re: problem with cross-dev gdb
Date: Mon, 10 Sep 2001 12:51:00 -0000	[thread overview]
Message-ID: <20010910153052.A18403@nevyn.them.org> (raw)
In-Reply-To: <OFB2CE9423.E7630EE4-ONC1256AC3.0067ED54@diamond.philips.com>

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


  reply	other threads:[~2001-09-10 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10 12:15 toon.diels
2001-09-10 12:51 ` Daniel Jacobowitz [this message]
2001-09-17  8:50 toon.diels
2001-09-18  6:29 ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010910153052.A18403@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=toon.diels@philips.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox