From: Dave Jones <davej@redhat.com>
To: Ildar Muslukhov <ildarm@google.com>
Cc: trinity@vger.kernel.org
Subject: Re: [PATCH] add parameter to explicitly select 32 or 64 bit variant of syscalls
Date: Mon, 16 Sep 2013 14:14:05 -0400 [thread overview]
Message-ID: <20130916181405.GA13688@redhat.com> (raw)
In-Reply-To: <52339222.2090403@google.com>
On Fri, Sep 13, 2013 at 03:30:58PM -0700, Ildar Muslukhov wrote:
> This patch enables explicit selection of 32 or 64 bit version of
> syscall(s) via parameter.
This version gets the tab/spacing right, but is word-wrapped..
> @@ -60,8 +63,9 @@ static void usage(void)
> fprintf(stderr, " --syslog,-S: log important info to syslog. (useful
> if syslog is remote)\n");
> fprintf(stderr, " --verbose,-v: increase output verbosity.\n");
> fprintf(stderr, " --victims,-V: path to victim files.\n");
> + fprintf(stderr, " --arch, -a: selects syscalls for the specified
> architecture (32 or 64). Both by default.");
> fprintf(stderr, "\n");
> - fprintf(stderr, " -c#: target specific syscall (takes syscall name as
> parameter).\n");
> + fprintf(stderr, " -c#,@: target specific syscall (takes syscall name
> as parameter and @ as architecture. No @ defaults to both archs.).\n");
> fprintf(stderr, " -N#: do # syscalls then exit.\n");
> fprintf(stderr, " -p: pause after syscall.\n");
> fprintf(stderr, " -s#: use # as random seed.\n");
> @@ -86,6 +90,7 @@ static const struct option longopts[] = {
> { "syslog", no_argument, NULL, 'S' },
> { "victims", required_argument, NULL, 'V' },
> { "verbose", no_argument, NULL, 'v' },
> + { "arch", required_argument, NULL, 'a' },
> { NULL, 0, NULL, 0 } };
So I can't apply this.
Dave
prev parent reply other threads:[~2013-09-16 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 22:30 [PATCH] add parameter to explicitly select 32 or 64 bit variant of syscalls Ildar Muslukhov
2013-09-16 18:14 ` Dave Jones [this message]
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=20130916181405.GA13688@redhat.com \
--to=davej@redhat.com \
--cc=ildarm@google.com \
--cc=trinity@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.