From: Daniel Jacobowitz <drow@mvista.com>
To: Dan Kegel <dkegel@ixiacom.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver multithread support broken in 5.2.1?
Date: Mon, 29 Jul 2002 06:39:00 -0000 [thread overview]
Message-ID: <20020729133931.GA2090@nevyn.them.org> (raw)
In-Reply-To: <3D41EF27.9070204@ixiacom.com>
On Fri, Jul 26, 2002 at 05:53:59PM -0700, Dan Kegel wrote:
> With gdb+dejagnu-weekly-CVS-20020709, remote debugging works fine on ppc405.
>
> With gdb-5.2.1 built the same way, it doesn't seem to work, and I
> get the error message
> GDB bug: target.c (target_signal_from_host): unrecognized real-time signal
> from gdbserver.
CVS branches strike again. 5.2.1 is a maintenance release only; it
contains some important bugfixes. CVS-20020709 is a development
snapshot, from the main trunk. It contains new features, like the
multithreaded gdbserver. If you want a released version of GDB with
this support, you have to wait for 5.3 (or 6.0, whatever we settle
on...). September was the plan, if I remember right.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-07-29 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 17:12 Dan Kegel
2002-07-29 6:39 ` Daniel Jacobowitz [this message]
2002-07-29 8:44 ` Andrew Cagney
2002-07-29 10:34 ` Dan Kegel
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=20020729133931.GA2090@nevyn.them.org \
--to=drow@mvista.com \
--cc=dkegel@ixiacom.com \
--cc=gdb@sources.redhat.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