linux-mips
[Top] [All Lists]

Re: cannot debug multi-threaded programs with gdb/gdbserver

To: Daniel Jacobowitz <dan@debian.org>
Subject: Re: cannot debug multi-threaded programs with gdb/gdbserver
From: "Steven J. Hill" <sjhill@realitydiluted.com>
Date: Tue, 17 Sep 2002 14:46:29 -0500
Cc: Stuart Hughes <seh@zee2.com>, Linux-MIPS <linux-mips@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <3D876053.C2CD1D8C@zee2.com> <3D87653E.9030702@realitydiluted.com> <20020917182536.GA25012@nevyn.them.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913 Debian/1.1-1
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.

-Steve


<Prev in Thread] Current Thread [Next in Thread>