From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Merge of nickrob-async-20060513 to mainline?
Date: Fri, 29 Sep 2006 01:50:00 -0000 [thread overview]
Message-ID: <17692.31519.429360.257622@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20060926222406.GA30535@nevyn.them.org>
[-- Attachment #1: message body and .signature --]
[-- Type: text/plain, Size: 1409 bytes --]
> > Perhaps I can use __WALL as a catch all.
>
> There's supposedly some supported kernel versions left where that
> didn't work.
OK, but this approach (using waitpid (-1, &status, WNOHANG | __WALL); in
gdb_wait_for_event) looks more promising than nickrob-async-20060513. It
didn't work with pthreads because the thread is _always_ waiting and receives
status information that other parts of the code waits on. Multi-thread tests
now work. Ignoring sigstep.exp (which doesn't work on mainline for me now
anyway), I get:
=== gdb Summary ===
# of expected passes 10707
# of unexpected failures 55
# of unexpected successes 1
# of expected failures 42
# of unknown successes 3
# of known failures 70
# of unresolved testcases 103
# of untested testcases 5
# of unsupported tests 4
with fails (where mainline doesn't) that include:
1) checkpoint.exp, mult-forks.exp which fail with
"ERROR: internal buffer is full." because the message
"select: Bad file descriptor" is repeatedly generated.
2) A couple of fails in attach.exp, define.exp
3) Extra failures in staticthreads.exp
I attach the compressed diff (28 Sep 2006) below. I put the line:
set GDBFLAGS "--async"
at the end of site.exp for the tests. Asynchronous output from MI requires
new tests but I haven't included these in the diff.
--
Nick http://www.inet.net.nz/~nickrob
[-- Attachment #2: Asynchronous GDB --]
[-- Type: application/octet-stream, Size: 43097 bytes --]
next prev parent reply other threads:[~2006-09-29 1:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 2:27 Nick Roberts
2006-08-30 2:33 ` Daniel Jacobowitz
2006-08-30 3:21 ` Nick Roberts
2006-08-30 4:01 ` Daniel Jacobowitz
2006-08-30 12:31 ` Eli Zaretskii
2006-08-30 21:34 ` Nick Roberts
2006-08-30 21:43 ` Daniel Jacobowitz
2006-08-30 23:45 ` Nick Roberts
2006-09-26 8:41 ` Nick Roberts
2006-09-26 12:38 ` Daniel Jacobowitz
2006-09-26 22:12 ` Nick Roberts
2006-09-26 22:24 ` Daniel Jacobowitz
2006-09-26 23:40 ` Nick Roberts
2006-09-29 1:50 ` Nick Roberts [this message]
2006-10-06 0:53 ` Nick Roberts
2006-10-06 1:26 ` Daniel Jacobowitz
2006-10-06 2:13 ` Nick Roberts
2006-10-06 3:24 ` Daniel Jacobowitz
2006-10-08 3:46 ` Nick Roberts
2006-10-09 18:00 ` async implies sync, was " Michael Snyder
2006-10-09 20:28 ` async implies sync Nick Roberts
2006-08-31 21:03 ` Merge of nickrob-async-20060513 to mainline? Mark Kettenis
2006-08-31 21:49 ` Nick Roberts
2006-08-31 22:29 ` Daniel Jacobowitz
2006-08-31 22:40 ` Nick Roberts
2006-08-31 22:53 ` Michael Snyder
2006-08-31 23:33 ` Nick Roberts
2006-08-31 23:37 ` Daniel Jacobowitz
2006-08-31 23:59 ` Jim Ingham
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=17692.31519.429360.257622@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb@sources.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