From: Daniel Jacobowitz <dan@debian.org>
To: Johannes Stezenbach <js@convergence.de>
Cc: "Steven J. Hill" <sjhill@realitydiluted.com>,
Stuart Hughes <seh@zee2.com>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: cannot debug multi-threaded programs with gdb/gdbserver
Date: Wed, 18 Sep 2002 09:23:53 -0400 [thread overview]
Message-ID: <20020918132353.GA16211@nevyn.them.org> (raw)
In-Reply-To: <20020918121047.GA17744@convergence.de>
On Wed, Sep 18, 2002 at 02:10:47PM +0200, Johannes Stezenbach wrote:
> Steven J. Hill wrote:
> > Stuart Hughes wrote:
> > >
> > >Does anyone know whether there is some special setup needed on
> > >gdb/gdbserver to use the multi-threaded gdbserver ??
> ...
> > >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.
>
> Is this a general recommendation to avoid H.J. Lu's binutils, or do
> you just favor the newer binutils version?
> What about binutils 2.13.90.0.4?
>
> I'm currently using gcc-2.95.4 with the Debian patches, and
> binutils binutils-2.12.90.0.14, which seem to work well.
> I planned to switch to gcc-3.2 but postponed it because I
> read about the DWARF debugging problems. Are they solved
> with gcc-3.2 / binutils-2.13 / gdb-5.3-CVS ?
Yes, they are fixed.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-09-18 13: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
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 [this message]
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=20020918132353.GA16211@nevyn.them.org \
--to=dan@debian.org \
--cc=js@convergence.de \
--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