public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: dvlasenk@sourceware.org To: systemtap-cvs@sourceware.org Subject: tests/ptrace-tests STATUS.tests test-template. ... Date: Tue, 03 Feb 2009 16:06:00 -0000 [thread overview] Message-ID: <20090203160625.2013.qmail@sourceware.org> (raw) CVSROOT: /cvs/systemtap Module name: tests Changes by: dvlasenk@sourceware.org 2009-02-03 16:06:25 Modified files: ptrace-tests : STATUS.tests test-template.c ptrace-tests/biarch-tests: .cvsignore ptrace-tests/tests: .cvsignore Makefile.am Added files: ptrace-tests/tests: waitpid-double-report.c Log message: waitpid-double-report.c: new testcase, see https://bugzilla.redhat.com/show_bug.cgi?id=481199 STATUS.tests: note that ptrace_cont-defeats-sigblock bossibly broke in 2.6.29-rc1 test-template.c: minor tweaks Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/tests/ptrace-tests/STATUS.tests.diff?cvsroot=systemtap&r1=1.8&r2=1.9 http://sourceware.org/cgi-bin/cvsweb.cgi/tests/ptrace-tests/test-template.c.diff?cvsroot=systemtap&r1=1.3&r2=1.4 http://sourceware.org/cgi-bin/cvsweb.cgi/tests/ptrace-tests/biarch-tests/.cvsignore.diff?cvsroot=systemtap&r1=1.24&r2=1.25 http://sourceware.org/cgi-bin/cvsweb.cgi/tests/ptrace-tests/tests/waitpid-double-report.c.diff?cvsroot=systemtap&r1=NONE&r2=1.1 http://sourceware.org/cgi-bin/cvsweb.cgi/tests/ptrace-tests/tests/.cvsignore.diff?cvsroot=systemtap&r1=1.35&r2=1.36 http://sourceware.org/cgi-bin/cvsweb.cgi/tests/ptrace-tests/tests/Makefile.am.diff?cvsroot=systemtap&r1=1.46&r2=1.47
next reply other threads:[~2009-02-03 16:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-03 16:06 dvlasenk [this message] -- strict thread matches above, loose matches on Subject: below -- 2009-02-03 14:31 dvlasenk
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=20090203160625.2013.qmail@sourceware.org \ --to=dvlasenk@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --cc=systemtap@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).