From: Nick Roberts <nickrob@snap.net.nz>
To: gdb-patches@sources.redhat.com
Subject: Async patch (no. 3)
Date: Fri, 13 Oct 2006 08:36:00 -0000 [thread overview]
Message-ID: <17711.20298.658015.189122@kahikatea.snap.net.nz> (raw)
[-- Attachment #1: message body and .signature --]
[-- Type: text/plain, Size: 1075 bytes --]
This async patch gives the same test results for synchronous and asynchronous
operation. Ignoring sigstep.exp again, I get:
=== gdb Summary ===
# of expected passes 10851
# of unexpected failures 44
# of unexpected successes 1
# of expected failures 42
# of unknown successes 3
# of known failures 66
# of untested testcases 5
# of unsupported tests 5
for both modes. I also get the same result for current mainline GDB in CVS
(although in this case I sometimes get extra fails for schedlock.exp).
Currently it only works for i686-pc-linux-gnu and I've tried to hide it from
other architectures/OSes. The only visible change should be those made to MI.
If the global maintainers are agreeable, in principle, to it's inclusion after
the next release, I will tidy it up and provide a ChangeLog. I would
appreciate any clues as to where some things should go e.g waitpid in
event-loop.c to linux-nat.c? (How?)
This patch will make the branch nickrob-async-20060513 defunct.
--
Nick http://www.inet.net.nz/~nickrob
[-- Attachment #2: Asynchronous GDB --]
[-- Type: application/octet-stream, Size: 43891 bytes --]
next reply other threads:[~2006-10-13 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 8:36 Nick Roberts [this message]
2006-10-13 13:11 ` Daniel Jacobowitz
2006-10-13 19:15 ` Nick Roberts
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=17711.20298.658015.189122@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@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