Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "Marcin Kościelnicki" <koriakin@0x04.net>, qiyaoltc@gmail.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 01/13] gdb/linux-record: Add testcases for a few syscalls.
Date: Thu, 29 Oct 2015 13:03:00 -0000	[thread overview]
Message-ID: <5632035E.30809@redhat.com> (raw)
In-Reply-To: <1445521166-14492-1-git-send-email-koriakin@0x04.net>

On 10/22/2015 02:39 PM, Marcin Kościelnicki wrote:
> gdb/testsuite/ChangeLog:
> 
> 	* gdb.reverse/linux-fstatat-reverse.c: New test.
> 	* gdb.reverse/linux-fstatat-reverse.exp: New file.
> 	* gdb.reverse/linux-getresuid-reverse.c: New test.
> 	* gdb.reverse/linux-getresuid-reverse.exp: New file.
> 	* gdb.reverse/linux-pipe-reverse.c: New test.
> 	* gdb.reverse/linux-pipe-reverse.exp: New file.
> 	* gdb.reverse/linux-readv-reverse.c: New test.
> 	* gdb.reverse/linux-readv-reverse.exp: New file.
> 	* gdb.reverse/linux-recvmsg-reverse.c: New test.
> 	* gdb.reverse/linux-recvmsg-reverse.exp: New file.
> 	* gdb.reverse/linux-time-reverse.c: New test.
> 	* gdb.reverse/linux-time-reverse.exp: New file.
> 	* gdb.reverse/linux-waitpid-reverse.c: New test.
> 	* gdb.reverse/linux-waitpid-reverse.exp: New file.

Excellent, thank you!

I ran your tests against pristine/unfixed gdb, and linux-readv-reverse.exp
passes cleanly.  This is on x86_64.  Is that expected?  The comments in
the test seem to suggest it would fail.

> +++ b/gdb/testsuite/gdb.reverse/linux-fstatat-reverse.c
> @@ -0,0 +1,39 @@
> +/* This testcase is part of GDB, the GNU debugger.
> +
> +   Copyright 2008-2015 Free Software Foundation, Inc.
> +
> +   This program is free software; you can redistribute it and/or modify
> +   it under the terms of the GNU General Public License as published by
> +   the Free Software Foundation; either version 3 of the License, or
> +   (at your option) any later version.
> +
> +   This program is distributed in the hope that it will be useful,
> +   but WITHOUT ANY WARRANTY; without even the implied warranty of
> +   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +   GNU General Public License for more details.
> +
> +   You should have received a copy of the GNU General Public License
> +   along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
> +
> +#define _GNU_SOURCE
> +#include <unistd.h>
> +#include <fcntl.h>
> +#include <sys/stat.h>
> +
> +void marker1 ()

We follow GNU formatting in tests too, unless there's a good
reason not to.  So, line break after void.  Also, this is C,
so write "(void)" for parameters.  Thus:

void
marker1 (void)
{


> +{
> +}
> +
> +void marker2 ()

Likewise.

> +{
> +}
> +
> +struct stat buf;
> +
> +int main() {

int
main ()
{


> +  marker1();
> +  int fd = open("/", O_PATH);
> +  fstatat(fd, ".", &buf, 0);
> +  marker2();

Space before parens.

Several of the test programs have non-conforming indentation too.

> +  return 0;
> +}
> diff --git a/gdb/testsuite/gdb.reverse/linux-fstatat-reverse.exp b/gdb/testsuite/gdb.reverse/linux-fstatat-reverse.exp
> new file mode 100644
> index 0000000..23652e4
> --- /dev/null
> +++ b/gdb/testsuite/gdb.reverse/linux-fstatat-reverse.exp
> @@ -0,0 +1,63 @@
> +# Copyright 2015 Free Software Foundation, Inc.
> +
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 3 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program.  If not, see <http://www.gnu.org/licenses/>.
> +
> +# This file is part of the gdb testsuite.
> +
> +#
> +# This test tests linux fstatat syscall for reverse execution.

Linux, uppercase.  But,

> +#
> +
> +if ![supports_reverse] {
> +    return
> +}
> +
> +
> +if ![istarget "*linux*"] then {
> +    verbose "Skipping linux syscall reverse tests."
> +    return
> +}

... I think most of these tests could/should drop this target check,
and drop the "linux-" in the filename as well.  Any target/port
that supports record/reverse execution should be able to run
this, as long as it manages to compile the test program.  And if the
test program doesn't compile in such a port, it'll be automatically
skipped.

> +
> +gdb_test "break marker1" \
> +    "Breakpoint $decimal at $hex: file .*$srcfile, line $decimal.*" \
> +    "set breakpoint at marker1"
> +
> +gdb_test "break marker2" \
> +    "Breakpoint $decimal at $hex: file .*$srcfile, line $decimal.*" \
> +    "set breakpoint at marker2"
> +
> +gdb_continue_to_breakpoint "marker1" ".*$srcfile:.*"
> +
> +gdb_continue_to_breakpoint "marker2" ".*$srcfile:.*"

Most (all?) these tests run to marker1 and then immediately to
marker2.  Can't they just continue to marker2 directly?

> +++ b/gdb/testsuite/gdb.reverse/linux-waitpid-reverse.exp

...

> +# will be remembered.  If not, new contents (status) will be # used, and

Spurious # after "will be".

> +# the test will fail.
> +
> +gdb_test "print status" ".* = -1" "check waitpid record"

Thanks,
Pedro Alves


  parent reply	other threads:[~2015-10-29 11:30 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-17 21:41 gdb/linux-record fixes Marcin Kościelnicki
2015-10-17 21:41 ` [PATCH 07/11] gdb/linux-record: Fix [sg]etgroups16 syscall Marcin Kościelnicki
2015-10-17 21:41 ` [PATCH 04/11] gdb/linux-record: Fix readdir and getdents handling Marcin Kościelnicki
2015-10-17 21:41 ` [PATCH 01/11] gdb/linux-record: Remove size_siginfo Marcin Kościelnicki
2015-10-17 21:41 ` [PATCH 11/11] gdb/linux-record: Fix struct sizes for x32 + aarch64 Marcin Kościelnicki
2015-10-17 21:41 ` [PATCH 08/11] gdb/linux-record: Fix newfstatat handling Marcin Kościelnicki
2015-10-17 21:41 ` [PATCH 09/11] gdb/linux-record: Fix old_select syscall handling Marcin Kościelnicki
2015-10-17 21:41 ` [PATCH 06/11] gdb/linux-record: Support time, waitpid, pipe syscalls Marcin Kościelnicki
2015-10-17 21:41 ` [PATCH 03/11] gdb/linux-record: Fix sizes of sigaction and sigset_t Marcin Kościelnicki
2015-10-17 21:49 ` [PATCH 10/11] gdb/linux-record: TASK_COMM_LEN is 16 on ppc too Marcin Kościelnicki
2015-10-17 21:49 ` [PATCH 05/11] gdb/linux-record: Fix msghdr parsing on 64-bit targets Marcin Kościelnicki
2015-10-17 21:49 ` [PATCH 02/11] gdb/linux-record: Fix size_[ug]id values Marcin Kościelnicki
2015-10-19 15:37 ` gdb/linux-record fixes Pedro Alves
2015-10-19 17:18   ` Marcin Kościelnicki
2015-10-20 11:07     ` Pedro Alves
2015-10-20 11:16       ` Marcin Kościelnicki
2015-10-22 13:39         ` Marcin Kościelnicki
2015-10-22 13:39           ` [PATCH v2 01/13] gdb/linux-record: Add testcases for a few syscalls Marcin Kościelnicki
2015-10-22 13:43             ` [PATCH v2 11/13] gdb/linux-record: TASK_COMM_LEN is 16 on ppc too Marcin Kościelnicki
2015-10-22 13:45             ` [PATCH v2 12/13] gdb/linux-record: Fix size_termios for x32, amd64, aarch64 Marcin Kościelnicki
2015-10-22 13:45             ` [PATCH v2 13/13] gdb/linux-record: Fix struct sizes for x32 Marcin Kościelnicki
2015-10-22 13:45             ` [PATCH v2 03/13] gdb/linux-record: Fix size_[ug]id values Marcin Kościelnicki
2015-10-22 13:49             ` [PATCH v2 10/13] gdb/linux-record: Fix old_select syscall handling Marcin Kościelnicki
2015-10-22 13:51             ` [PATCH v2 06/13] gdb/linux-record: Fix msghdr parsing on 64-bit targets Marcin Kościelnicki
2015-10-22 13:51             ` [PATCH v2 04/13] gdb/linux-record: Fix sizes of sigaction and sigset_t Marcin Kościelnicki
2015-10-22 13:55             ` [PATCH v2 07/13] gdb/linux-record: Support time, waitpid, pipe syscalls Marcin Kościelnicki
2015-10-22 14:32             ` [PATCH v2 02/13] gdb/linux-record: Remove size_siginfo Marcin Kościelnicki
2015-10-22 15:01             ` [PATCH v2 08/13] gdb/linux-record: Fix [gs]etgroups16 syscall Marcin Kościelnicki
2015-10-22 15:06             ` [PATCH v2 05/13] gdb/linux-record: Fix readdir and getdents handling Marcin Kościelnicki
2015-10-22 15:07             ` [PATCH v2 09/13] gdb/linux-record: Fix newfstatat handling Marcin Kościelnicki
2015-10-29 13:03             ` Pedro Alves [this message]
2015-10-29 13:03               ` [PATCH v2 01/13] gdb/linux-record: Add testcases for a few syscalls Marcin Kościelnicki
2015-10-30 14:52                 ` Pedro Alves
2015-10-30 10:36               ` Marcin Kościelnicki
2015-10-30 15:05                 ` Pedro Alves
2015-11-02  1:34                   ` Marcin Kościelnicki
2015-11-02 16:40                     ` Pedro Alves
2015-11-02 18:53                       ` [PATCH] gdb/reverse: Fix continue_to_breakpoint in syscall testcases Marcin Kościelnicki
2015-11-02 19:17                         ` Pedro Alves
2015-11-02 19:58                           ` [PATCH 1/2] " Marcin Kościelnicki
2015-11-02 19:58                             ` [PATCH 1/2] Obvious typo fix in gdb.reverse/readv-reverse.exp Marcin Kościelnicki
2015-11-02 20:00                               ` Pedro Alves
2015-11-02 19:59                             ` [PATCH 1/2] gdb/reverse: Fix continue_to_breakpoint in syscall testcases Pedro Alves
2015-10-30 10:37               ` [PATCH 01/13] gdb/record: Add testcases for a few syscalls Marcin Kościelnicki
2015-10-30 15:41                 ` Pedro Alves
2015-10-30 15:55                   ` [PATCH v4 " Marcin Kościelnicki
2015-10-31 18:59                     ` Pedro Alves
2015-10-29 13:03           ` gdb/linux-record fixes Pedro Alves
2015-10-29 13:03             ` 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=5632035E.30809@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=koriakin@0x04.net \
    --cc=qiyaoltc@gmail.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