From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
Cc: "Ecos-List \(E-mail\)" <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Multi thread Debugging
Date: Thu, 24 Aug 2000 07:17:00 -0000 [thread overview]
Message-ID: <39A52E6E.1CFF3446@redhat.co.uk> (raw)
In-Reply-To: <8AE4B526B977D411841F00A0CC334020052C23@cuz-exchange.sdesigns.net>
Fabrice Gautier wrote:
>
> In order to workaround this problem I put a breakpoint in cyg_thread_create
> and I recorded every thread structures so I can watch them later.
>
> And doing so I saw that the hwthread->saved_context member is always a NULL
> pointer (for every thread and all the time)
Then you should probably be looking at interrupt_end in
kernel/VERSION/src/intr/intr.cxx to see what's going on there - in
particular, is the "regs" argument valid.
> Is this normal? Is this is not structure used by the stub/gdb to access
> threads informations??
Remind us which target and platform you are using?
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-08-24 7:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-23 14:53 Fabrice Gautier
2000-08-24 7:17 ` Jonathan Larmour [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-01 14:18 Fabrice Gautier
2000-08-31 18:54 Fabrice Gautier
2000-09-01 3:12 ` Nick Garnett
2000-08-31 15:31 Fabrice Gautier
2000-09-01 2:55 ` Nick Garnett
2000-08-31 3:56 Fabrice Gautier
2000-08-30 19:56 Fabrice Gautier
2000-08-31 4:15 ` Nick Garnett
2000-08-30 16:39 Fabrice Gautier
2000-08-25 12:06 Fabrice Gautier
2000-08-25 11:18 Fabrice Gautier
2000-08-25 11:38 ` Jonathan Larmour
2000-08-21 19:15 Fabrice Gautier
2000-08-15 12:00 Fabrice Gautier
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=39A52E6E.1CFF3446@redhat.co.uk \
--to=jlarmour@redhat.co.uk \
--cc=Fabrice_Gautier@sdesigns.com \
--cc=ecos-discuss@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).