From: Joel Brobecker <brobecker@adacore.com>
To: Rob Quill <rob.quill@gmail.com>
Cc: Michael Snyder <Michael.Snyder@palmsource.com>, gdb@sourceware.org
Subject: Re: Single stepping and threads
Date: Sat, 02 Dec 2006 16:36:00 -0000 [thread overview]
Message-ID: <20061202163654.GS3304@adacore.com> (raw)
In-Reply-To: <baf6008d0612020827y3fd13229v16e14c24da321e6a@mail.gmail.com>
> I fail to see how stopping all threads and just going forward with one
> should stop "correct" code from executiong properly.
Consider a rendez-vous, for instance. I'm not sure if a "rendez-vous"
is a universal term or not, so I'll briefly explain what I mean:
"rendez-vous" is used in Ada speak to represent a situation where
one task is blocked waiting for another task to call one of its
entries; neither task is allowed to run until both tasks reach the
entry.
Back to our question: If one of the tasks is not running, it cannot
reach its entry, and thus the other task gets stuck on that entry call.
--
Joel
next prev parent reply other threads:[~2006-12-02 16:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 5:29 Daniel Jacobowitz
2006-11-29 5:58 ` Joel Brobecker
2006-11-29 13:25 ` Daniel Jacobowitz
2006-11-29 16:38 ` Joel Brobecker
2006-11-30 13:54 ` Daniel Jacobowitz
2006-11-30 23:36 ` Michael Snyder
2006-11-30 23:54 ` Joel Brobecker
2006-12-01 1:02 ` Daniel Jacobowitz
2006-12-01 22:43 ` Michael Snyder
2006-12-02 16:27 ` Rob Quill
2006-12-02 16:33 ` Daniel Jacobowitz
2006-12-02 16:36 ` Joel Brobecker [this message]
2006-12-04 19:50 ` Michael Snyder
2006-11-30 8:44 ` Robert Dewar
2006-11-30 23:32 ` Michael Snyder
2006-11-30 23:26 ` Michael Snyder
2006-11-30 23:31 ` Joel Brobecker
2006-11-29 12:41 ` Mark Kettenis
2006-11-29 13:36 ` Daniel Jacobowitz
2006-11-30 23:38 ` Michael Snyder
2006-11-30 23:22 ` Michael Snyder
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=20061202163654.GS3304@adacore.com \
--to=brobecker@adacore.com \
--cc=Michael.Snyder@palmsource.com \
--cc=gdb@sourceware.org \
--cc=rob.quill@gmail.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