From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: holger.vogt@uni-duisburg.de, gdb@sources.redhat.com
Subject: Re: w32api fibers supported?
Date: Thu, 14 Jun 2001 02:40:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20010614112934.01cbcab0@ics.u-strasbg.fr> (raw)
In-Reply-To: <3B287012.99E9247E@unidui.uni-duisburg.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
At 10:04 14/06/01 , Holger Vogt a écrit:
>Hi,
>
>in CYGWIN or MINGW32 you may use fibers as "lightweight" threads
>(defined in w32api). I tried to port SystemC (using fibers) to CYGWIN
>but ran into difficulties.
>
>Using gdb to debug yields inconsistent results. A simple testcase exits
>in gdb with error code returned but runs o.k. outside gdb (gdb 4.18 and
>5.0).
>
>Are fibers supported in gdb? Is there a simple way to allow debugging
>applications with fibers?
This will probably be difficult,
because the kernel API doesn't generate
any debugger info when a fiber is created.
To support this, a special drivers that intercepts
all these Fiber functions and calls the Debugger would be needed ...
Without it, GDB will continue to consider that you run a simple thread.
But I don't really understand what you mean by saying that it yields
inconsistent results.
Could you try to be a little more explicit ?
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
next prev parent reply other threads:[~2001-06-14 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-14 0:59 Holger Vogt
2001-06-14 2:40 ` Pierre Muller [this message]
2001-06-16 1:02 ` Holger Vogt
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=4.2.0.58.20010614112934.01cbcab0@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=gdb@sources.redhat.com \
--cc=holger.vogt@uni-duisburg.de \
/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