From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/8] Fix PR gdb/14766; cleanup foll-vfork.exp and extend it.
Date: Thu, 25 Oct 2012 17:42:00 -0000 [thread overview]
Message-ID: <20121025174002.13324.8164.stgit@brno.lan> (raw)
Running the whole testsuite with single-step forced and using software
single-step on amd64 (that's quite painful, but catches a lot of
interesting corner cases) revealed gdb/14766 (I no longer off hand
remember the details of why that triggers there, but that's
unimportant). This series fixes that PR. It starts by modernizing
foll-vfork.exp, and then extending it to cover more cases, exposing
the bug on hardware step targets (like amd64 GNU/Linux). I've kept
the tests patches split by incremental logical changes, as otherwise
the test additions/changes combined would be incompreensible and look
like a complete rewrite.
Barring objections, comments, etc., I'll commit this after a short
while.
Tested on amd64 Fedora 17.
---
Pedro Alves (8):
foll-vfork.exp: Modernize.
foll-vfork.exp: Don't hard code line numbers.
foll-vfork.exp: Expose more testing on non-HP/UX targets
foll-vfork.c/vforked-prog.c: Add copyright headers.
foll-vfork.exp: Use with_test_prefix.
foll-vfork.exp: Clean restart gdb before each test procedure.
foll-vfork.exp: Also test following vfork when the child exits.
Fix PR gdb/14766 - vfork child exit with "set follow-fork-mode child" broken.
--
Pedro Alves
next reply other threads:[~2012-10-25 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 17:42 Pedro Alves [this message]
2012-10-25 17:42 ` [PATCH 6/8] foll-vfork.exp: Clean restart gdb before each test procedure Pedro Alves
2012-11-02 18:18 ` Pedro Alves
2012-10-25 17:42 ` [PATCH 2/8] foll-vfork.exp: Don't hard code line numbers Pedro Alves
2012-10-25 17:42 ` [PATCH 7/8] foll-vfork.exp: Also test following vfork when the child exits Pedro Alves
2012-10-25 17:42 ` [PATCH 8/8] Fix PR gdb/14766 - vfork child exit with "set follow-fork-mode child" broken Pedro Alves
2012-10-25 17:49 ` Pedro Alves
2012-10-25 17:42 ` [PATCH 5/8] foll-vfork.exp: Use with_test_prefix Pedro Alves
2012-10-25 17:42 ` [PATCH 3/8] foll-vfork.exp: Expose more testing on non-HP/UX targets Pedro Alves
2012-10-25 17:42 ` [PATCH 4/8] foll-vfork.c/vforked-prog.c: Add copyright headers Pedro Alves
2012-10-25 17:42 ` [PATCH 1/8] foll-vfork.exp: Modernize Pedro Alves
2012-10-30 20:50 ` [PATCH 0/8] Fix PR gdb/14766; cleanup foll-vfork.exp and extend it Tom Tromey
2012-11-02 18:15 ` Pedro Alves
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=20121025174002.13324.8164.stgit@brno.lan \
--to=palves@redhat.com \
--cc=gdb-patches@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