From: Phil Muldoon <pmuldoon@redhat.com>
To: Rick Moseley <rmoseley@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: Changes
Date: Thu, 10 Jul 2008 13:26:00 -0000 [thread overview]
Message-ID: <48760DD4.8060207@redhat.com> (raw)
In-Reply-To: <48760B1E.3060709@redhat.com>
Rick Moseley wrote:
>>
>> Ditto. I will bring it up again when the time is right.
>>
>>
> Agreed too. The ability to catch a task as it is abnormally
> terminating and bring up the debugger is a powerful thing IMHO. I
> don't see any need here to involve another app(Systemtap has been
> mentioned) to perform this feature. I don't remember this being too
> difficult in Frysk(although I am not the one that implemented it.)
>
The (three) Frysk state machines are what catches that, and that is a
considerable amount of complex code. Modelling a thread is delicate,
complex and very fuzzy. Take a look at LinuxWaitBuilder and how it has
to do backflips to catch out of order wait notifications. But I think
the issue is not catching a thread as it spawns another - we will have
to have that. That's in the goals. Follow fork, follow clone - these
are a intrinsic to the scalability goal of working with many threads
(imho ;))
It's all the other always-on, low-cost monitoring goals that Systemtap
do now I think are being excluded.
Regards
Phil
next prev parent reply other threads:[~2008-07-10 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 22:19 Changes Tom Tromey
2008-07-10 0:06 ` Changes Sami Wagiaalla
2008-07-11 17:04 ` Changes Sami Wagiaalla
2008-07-10 4:17 ` Changes Thiago Jung Bauermann
2008-07-10 5:43 ` Changes Sami Wagiaalla
2008-07-10 13:14 ` Changes Rick Moseley
2008-07-10 13:26 ` Phil Muldoon [this message]
2008-07-10 17:07 ` Changes Eric Bachalo
2008-07-10 19:43 ` Changes Dodji Seketeli
2008-07-11 16:55 ` Changes Tom Tromey
2008-07-10 8:24 ` Changes Phil Muldoon
2008-07-11 10:44 ` Changes Phil Muldoon
2008-07-17 7:51 ` Changes Jan Blunck
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=48760DD4.8060207@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@sourceware.org \
--cc=rmoseley@redhat.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).