All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Eric Blake" <eblake@redhat.com>,
	"Lluís Vilanova" <vilanova@ac.upc.edu>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 3/3] tracetool: report error on foo() instead of foo(void)
Date: Wed, 10 Jan 2018 20:25:53 +0000	[thread overview]
Message-ID: <20180110202553.31889-4-stefanha@redhat.com> (raw)
In-Reply-To: <20180110202553.31889-1-stefanha@redhat.com>

C functions with no arguments must be declared foo(void) instead of
foo().  The tracetool argument list parser has never accepted an empty
argument list.  This patch adds a clear error message for this error
case.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 scripts/tracetool/__init__.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/scripts/tracetool/__init__.py b/scripts/tracetool/__init__.py
index 5db1f5c395..8e9efba78f 100644
--- a/scripts/tracetool/__init__.py
+++ b/scripts/tracetool/__init__.py
@@ -75,6 +75,8 @@ class Arguments:
         res = []
         for arg in arg_str.split(","):
             arg = arg.strip()
+            if not arg:
+                raise ValueError("Empty argument (did you forget to use 'void'?)")
             if arg == 'void':
                 continue
 
-- 
2.14.3

  parent reply	other threads:[~2018-01-10 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 20:25 [Qemu-devel] [PATCH 0/3] tracetool: improve error messages Stefan Hajnoczi
2018-01-10 20:25 ` [Qemu-devel] [PATCH 1/3] tracetool: prefix parse errors with line numbers Stefan Hajnoczi
2018-01-10 20:47   ` Eric Blake
2018-01-10 20:25 ` [Qemu-devel] [PATCH 2/3] tracetool: clarify that "formats" means "format strings" Stefan Hajnoczi
2018-01-10 20:25 ` Stefan Hajnoczi [this message]
2018-01-10 20:48 ` [Qemu-devel] [PATCH 0/3] tracetool: improve error messages Eric Blake
2018-01-15 14:03   ` Stefan Hajnoczi
2018-01-10 21:06 ` no-reply
2018-01-15 14:11 ` Stefan Hajnoczi

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=20180110202553.31889-4-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vilanova@ac.upc.edu \
    /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.