From: Daniel Jacobowitz <drow@mvista.com>
To: toon.diels@philips.com
Cc: gdb@sourceware.cygnus.com
Subject: Re: problem with cross-dev gdb
Date: Tue, 18 Sep 2001 06:29:00 -0000 [thread overview]
Message-ID: <20010918092825.A29850@nevyn.them.org> (raw)
In-Reply-To: <OF40A87756.1F46BE44-ONC1256ACA.005511E8@diamond.philips.com>
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
next prev parent reply other threads:[~2001-09-18 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 8:50 toon.diels
2001-09-18 6:29 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-10 12:15 toon.diels
2001-09-10 12:51 ` 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=20010918092825.A29850@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