From: Daniel Jacobowitz <drow@mvista.com>
To: Miah Gregory <miah@picsel.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb/threading under arm-linux
Date: Tue, 05 Mar 2002 07:35:00 -0000 [thread overview]
Message-ID: <20020305103521.A27860@nevyn.them.org> (raw)
In-Reply-To: <908b78124b.miah@picsel.com>
On Tue, Mar 05, 2002 at 01:39:31PM +0000, Miah Gregory wrote:
> Hi,
>
> Does anyone know whether threads are supported in the arm-linux version of
> gdb. From the gdb documentation, if 'info threads' appears to no-op, and
> 'thread x' gives an error, threads are not supported.
>
> I'm trying to work out whether I'm seeing a gdb problem, a kernel problem,
> or both. I'm running this test on a pair of compaq ipaq's, one running
> 2.4.3-rmk2-np1, and the other running 2.4.16-rmk1.
>
> gdb version | kernel version | threads seem to work?
> ------------|----------------|-------------------------------------
> 5.0 | 2.4.3-rmk2-np1 | Yes
> 5.1.1 | 2.4.3-rmk2-np1 | No, but lots of SIG32's are received
> 5.0 | 2.4.16-rmk1 | No, but lots of SIG32's are received
> 5.1.1 | 2.4.16-rmk1 | No, but lots of SIG32's are received
>
> I'm happy to try and debug this, but I could do with a few pointers as to
> where I should start looking, and some ideas as to what I'm looking for.
>
> Thanks in advance.
Please try a current snapshot (see http://sources.redhat.com/gdb/). It
should work.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-05 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 5:39 Miah Gregory
2002-03-05 7:35 ` Daniel Jacobowitz [this message]
2002-03-06 1:45 ` Miah Gregory
2002-03-06 1:51 ` Miah Gregory
2002-03-06 17:32 ` Michael Snyder
2002-03-13 5:13 ` Miah Gregory
[not found] ` <20020306110033.A14410@nevyn.them.org>
2002-03-13 5:12 ` Miah Gregory
2002-03-13 9:09 ` Daniel Jacobowitz
2002-03-13 9:44 ` Miah Gregory
2002-03-13 9:50 ` Daniel Jacobowitz
2002-03-13 9:36 ` Kevin Buettner
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=20020305103521.A27860@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=miah@picsel.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