From: Jonathan Larmour <jlarmour@cygnus.co.uk>
To: Andrew Lunn <lunn@ma.tech.ascom.ch>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] info threads on Synthetic target
Date: Fri, 24 Sep 1999 08:27:00 -0000 [thread overview]
Message-ID: <37EB9802.C5C795B7@cygnus.co.uk> (raw)
In-Reply-To: <199909241450.QAA01842@biferten.ma.tech.ascom.ch>
Andrew Lunn wrote:
>
> Hi Folks
>
> For the Synthetic linux target, is gdb supposed to be able to see the
> threads? The "info threads" command does not work. I have the HAL
> option CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT enabled.
Simple answer: nope. It would require gdb support to be added I'm afraid.
Jifl
--
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK. Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
my brains kept falling out." || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/ These opinions are all my own fault
next prev parent reply other threads:[~1999-09-24 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-24 7:52 Andrew Lunn
1999-09-24 8:27 ` Jonathan Larmour [this message]
1999-09-24 10:16 ` [ECOS] " Bart Veer
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=37EB9802.C5C795B7@cygnus.co.uk \
--to=jlarmour@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=lunn@ma.tech.ascom.ch \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).