From: Stan Cox <scox@redhat.com>
To: Frysk List <frysk@sourceware.org>
Subject: Re: meeting 2006-12-05
Date: Tue, 05 Dec 2006 21:13:00 -0000 [thread overview]
Message-ID: <1165353031.20351.134.camel@multics.rdu.redhat.com> (raw)
In-Reply-To: <4575BC34.3010506@redhat.com>
Testing
Most failures are due to build tree versus install tree testing.
Kernel
218404 zombied process now has tasks/ not a bug (close, cagney)
218405 /proc/PID/task lags behind thread exit and join
main thread thinks subthreads are gone.
/proc info is probably lagging.
Explicitly check for thread status
217433 'X' state of un-joined thread no longer occurs
Similar to 218405
218410 non-main task's exited status lost when tracing
Special semantics for sigchild. The thread about to stop sends a
sigchild to the parent but there is a delay until this is visible with
a wait so that nohang doesn't hang. Difference in behavior is possibly
luck. Event loop implemented using SIGCHILD. Could also use SIGIO,
but this is not how it is implemented. (roland evaluation)
217809 waitpid hangs on dieing process
regression test would help but testcase may be as good as we will get.
216150 waitpid returns WIFSIGNALED instead of WIFEXITED
roland has a fix
jankratochvil is available for looking at libelf bugs.
Stepping
step over/step out (mcvet)
Meeting (cagney, mjw, mcvet)
Breakpoints
hpd support added for breakpoints.
gui support (timoore)
Commands
core refactoring (pmuldoon)
fstack unmangling,dejagnu (npremji)
Docs
doc plan (rmoseley)
Misc
console window still locks up
-doesn't lock up on FC6, but doesn't work
unmangling (scox)
prev parent reply other threads:[~2006-12-05 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 18:36 Andrew Cagney
2006-12-05 21:13 ` Stan Cox [this message]
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=1165353031.20351.134.camel@multics.rdu.redhat.com \
--to=scox@redhat.com \
--cc=frysk@sourceware.org \
/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).