From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: Stuart Hughes <seh@zee2.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: cannot debug multi-threaded programs with gdb/gdbserver
Date: Tue, 17 Sep 2002 12:24:14 -0500 [thread overview]
Message-ID: <3D87653E.9030702@realitydiluted.com> (raw)
In-Reply-To: 3D876053.C2CD1D8C@zee2.com
Stuart Hughes wrote:
>
> Does anyone know whether there is some special setup needed on
> gdb/gdbserver to use the multi-threaded gdbserver ??
>
Wow, there are so many things to tell you...where to start...
> My environment is as follows:
>
> CPU: NEC VR5432
> kernel: linux-2.4.18 + patches
> glibc: 2.2.3 + patches
> gdb: 5.2/3 from CVS
>
Has to be the gdb-5.3 branch...go look at http://sources.redhat.com/gdb
> gcc: 3.1
> binutils: Version 2.11.90.0.25
>
Don't use H.J. Lu's binutils, use the released one. Use gcc-3.2 and
binutils-2.13 as they have fixes for the MIPS debugging symbols with
regards to DWARF.
> 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.
> gdbserver configured using:
>
> configure --prefix=/usr --host=mipsel-linux --target=mipsel-linux
> --enable-threads --enable-shared
>
I would also try 'CC=mipsel-linux-gcc configure <...>'.
-Steve
next prev parent reply other threads:[~2002-09-17 17:24 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 [this message]
2002-09-17 18:25 ` Daniel Jacobowitz
2002-09-17 19:46 ` Steven J. Hill
2002-09-17 20:47 ` Daniel Jacobowitz
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=3D87653E.9030702@realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=linux-mips@linux-mips.org \
--cc=seh@zee2.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.