From: Jesper Skov <jskov@cygnus.co.uk>
To: "Patrick O'Grady" <patrick@plasticgrape.com>
Cc: ecos-discuss@sourceware.cygnus.com,
Roland Schwarz <roland.schwarz@telecom.at>
Subject: Re: [ECOS] probably a FAQ, but: how many x86 ports are in motion out there?
Date: Fri, 08 Oct 1999 01:45:00 -0000 [thread overview]
Message-ID: <otemf6guwq.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <Pine.BSF.4.05.9910070937100.48573-100000@pru.plasticgrape.com>
>>>>> "Patrick" == Patrick O'Grady <patrick@plasticgrape.com> writes:
[snip]
Patrick> - The GDB stub is about 75% in place. It doesn't know
Patrick> anything about threads yet, and some of the exceptions aren't
Patrick> supported properly. However, the breakpoint exception, is
Patrick> working great.
Patrick> - I've just yesterday been able to get the clock ISR to work,
Patrick> so the threading support is next on the list.
[snip]
Patrick> I'm hoping to have the threading stuff figured out by the end
Patrick> of next week--I'll post it as soon as I feel like it's
Patrick> usable! Stay tuned...
Is it kernel thread support or GDB thread debugging support you want
to implement? The latter should come pretty much free with the
hal/common stub code.
Jesper
next prev parent reply other threads:[~1999-10-08 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 9:29 Roland Schwarz
1999-10-07 9:53 ` [ECOS] probably a FAQ, but: how many x86 ports are in motionout there? Patrick O'Grady
1999-10-08 1:45 ` Jesper Skov [this message]
1999-10-11 13:03 ` [ECOS] hal/i386/pc Patrick O'Grady
1999-10-12 1:29 ` [ECOS] hal/i386/pc Jesper Skov
-- strict thread matches above, loose matches on Subject: below --
1999-03-03 14:55 [ECOS] probably a FAQ, but: how many x86 ports are in motion out there? alex
1999-02-25 13:49 The Utz Family
1999-03-02 13:56 ` 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=otemf6guwq.fsf@thinktwice.zoftcorp.dk \
--to=jskov@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=patrick@plasticgrape.com \
--cc=roland.schwarz@telecom.at \
/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).