public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/12649] reproducer for races of expect incomplete reads Date: Wed, 20 Aug 2014 18:23:00 -0000 [thread overview] Message-ID: <bug-12649-4717-sX1wrSv4sM@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12649-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=12649 --- Comment #15 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via 2a31c6236de308f7109720230e70b96c5d5b966a (commit) from 469a34932ae4208240e98c843b01ea1f00892137 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2a31c6236de308f7109720230e70b96c5d5b966a commit 2a31c6236de308f7109720230e70b96c5d5b966a Author: Pedro Alves <palves@redhat.com> Date: Wed Aug 20 18:55:54 2014 +0100 Integrate PR 12649's race detector directly in the testsuite machinery This integrates Jan Kratochvil's nice race reproducer from PR testsuite/12649 into the testsuite infrustructure directly. With this, one only has to do either 'make check-read1' or 'make check READ1="1"' to preload the read1.so library into expect. Currently only enabled for glibc/GNU systems, and if build==host==target. gdb/testsuite/ChangeLog: * Makefile.in (EXTRA_RULES, CC): New variables, get from configure. (EXPECT): Handle READ1 being set. (all): Depend on EXTRA_RULES. (check-read1, expect-read1, read1.so, read1): New rules. * README (Testsuite Parameters): Document the READ1 make variable. (Race detection): New section. * configure: Regenerate. * configure.ac: If build==host==target, and running under a GNU/glibc system, add read1 to the extra Makefile rules. (EXTRA_RULES): AC_SUBST it. * lib/read1.c: New file. gdb/ChangeLog: * Makefile.in (check-read1): New rule. ----------------------------------------------------------------------- Summary of changes: gdb/ChangeLog | 4 ++ gdb/Makefile.in | 8 ++++ gdb/testsuite/ChangeLog | 16 +++++++ gdb/testsuite/Makefile.in | 44 ++++++++++++++++++-- gdb/testsuite/README | 41 ++++++++++++++++++ gdb/testsuite/configure | 10 ++++ gdb/testsuite/configure.ac | 9 ++++ .../expect-read1.c => testsuite/lib/read1.c} | 16 ++++---- 8 files changed, 136 insertions(+), 12 deletions(-) copy gdb/{contrib/expect-read1.c => testsuite/lib/read1.c} (80%) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-08-20 18:23 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-07 8:08 [Bug testsuite/12649] New: " jan.kratochvil at redhat dot com 2011-04-07 8:16 ` [Bug testsuite/12649] " jan.kratochvil at redhat dot com 2011-04-07 8:22 ` jan.kratochvil at redhat dot com 2011-04-07 10:35 ` pedro at codesourcery dot com 2011-04-12 9:26 ` mpolacek at redhat dot com 2011-05-02 17:52 ` cvs-commit at gcc dot gnu.org 2011-05-27 14:41 ` mpolacek at redhat dot com 2011-10-29 14:01 ` jan.kratochvil at redhat dot com 2011-11-25 23:53 ` cvs-commit at gcc dot gnu.org 2011-12-02 12:44 ` cvs-commit at gcc dot gnu.org 2011-12-10 23:05 ` cvs-commit at gcc dot gnu.org 2012-05-15 13:10 ` cvs-commit at gcc dot gnu.org 2012-07-04 14:57 ` cvs-commit at gcc dot gnu.org 2013-05-21 15:00 ` cvs-commit at gcc dot gnu.org 2014-06-02 15:22 ` polacek at redhat dot com 2014-08-20 18:23 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-14 14:50 ` ssbssa at sourceware dot org 2024-01-14 15:04 ` vries at gcc dot gnu.org
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=bug-12649-4717-sX1wrSv4sM@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).