From: Daniel Jacobowitz <dan@debian.org>
To: "Steven J. Hill" <sjhill@realitydiluted.com>
Cc: Stuart Hughes <seh@zee2.com>, Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: cannot debug multi-threaded programs with gdb/gdbserver
Date: Tue, 17 Sep 2002 16:47:29 -0400 [thread overview]
Message-ID: <20020917204729.GA31458@nevyn.them.org> (raw)
In-Reply-To: <3D878695.3040101@realitydiluted.com>
On Tue, Sep 17, 2002 at 02:46:29PM -0500, Steven J. Hill wrote:
> Daniel Jacobowitz wrote:
> >On Tue, Sep 17, 2002 at 12:24:14PM -0500, Steven J. Hill wrote:
> >
> >Steve, have you started memorizing my responses again? :)
> >
> *gurgle* Yeah, I have. I apologize if it seemed I was taking
> credit for anything.
>
> >>>cross-gdb configured using:
> >>>
> >>>configure --prefix=/usr --target=mipsel-linux --disable-sim
> >>>--disable-tcl --enable-threads --enable-shared
> >>>
> >>
> >>Use '--target=mips-linux' and you'll be better off. Don't worry, it
> >>will support both endians.
> >
> >
> >Except for this one - where'd that come from? It should make no
> >functional difference either way, at least assuming you always give GDB
> >a binary.
> >
> I got some weird errors (unfortunately I can't remember) if I tried
> using 'mipsel-linux' as the target. So you're saying that a gdb
> configured for 'mipsel-linux' or 'mips-linux' should work the same?
> Thanks Daniel.
Hmm, if you can reproduce these let me know what they are. I use a
mipsel GDB regularly.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-09-17 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 17:03 cannot debug multi-threaded programs with gdb/gdbserver Stuart Hughes
2002-09-17 17:24 ` Steven J. Hill
2002-09-17 18:25 ` Daniel Jacobowitz
2002-09-17 19:46 ` Steven J. Hill
2002-09-17 20:47 ` Daniel Jacobowitz [this message]
2002-09-18 7:48 ` Stuart Hughes
2002-09-18 12:10 ` Johannes Stezenbach
2002-09-18 13:23 ` 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=20020917204729.GA31458@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=seh@zee2.com \
--cc=sjhill@realitydiluted.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