qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Lluís Vilanova" <vilanova@ac.upc.edu>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH v4 8/8] trace: improve error reporting when parsing simpletrace header
Date: Wed, 25 Jan 2017 16:14:17 +0000	[thread overview]
Message-ID: <20170125161417.31949-9-berrange@redhat.com> (raw)
In-Reply-To: <20170125161417.31949-1-berrange@redhat.com>

When loading a simpletrace binary file we just report
"Not a valid trace file!" which is not very helpful. Report
exactly which field we found to be invalid.

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
---
 scripts/simpletrace.py | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/scripts/simpletrace.py b/scripts/simpletrace.py
index 4ca903d..4c99004 100755
--- a/scripts/simpletrace.py
+++ b/scripts/simpletrace.py
@@ -73,10 +73,14 @@ def read_record(edict, idtoname, fobj):
 def read_trace_header(fobj):
     """Read and verify trace file header"""
     header = read_header(fobj, log_header_fmt)
-    if header is None or \
-       header[0] != header_event_id or \
-       header[1] != header_magic:
+    if header is None:
         raise ValueError('Not a valid trace file!')
+    if header[0] != header_event_id:
+        raise ValueError('Not a valid trace file, header id %d != %d' %
+                         (header[0], header_event_id))
+    if header[1] != header_magic:
+        raise ValueError('Not a valid trace file, header magic %d != %d' %
+                         (header[1], header_magic))
 
     log_version = header[2]
     if log_version not in [0, 2, 3, 4]:
-- 
2.9.3

  parent reply	other threads:[~2017-01-25 16:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 16:14 [Qemu-devel] [PATCH v4 0/8] Switch all subdirs over to modular trace.h file Daniel P. Berrange
2017-01-25 16:14 ` [Qemu-devel] [PATCH v4 1/8] make: move top level dir to end of include search path Daniel P. Berrange
2017-01-25 16:25   ` Eric Blake
2017-02-04 15:48   ` Alberto Garcia
2017-02-06 10:42     ` Daniel P. Berrange
2017-01-25 16:14 ` [Qemu-devel] [PATCH v4 2/8] trace: move hw/block/dataplane events to correct subdir Daniel P. Berrange
2017-01-25 16:14 ` [Qemu-devel] [PATCH v4 3/8] trace: move hw/xen " Daniel P. Berrange
2017-01-25 16:14 ` [Qemu-devel] [PATCH v4 4/8] trace: move hw/i386/xen " Daniel P. Berrange
2017-01-25 16:14 ` [Qemu-devel] [PATCH v4 5/8] trace: move setting of group name into Makefiles Daniel P. Berrange
2017-01-25 16:14 ` [Qemu-devel] [PATCH v4 6/8] trace: switch to modular code generation for sub-directories Daniel P. Berrange
2017-01-25 16:14 ` [Qemu-devel] [PATCH v4 7/8] trace: update docs to reflect new code generation approach Daniel P. Berrange
2017-01-25 16:14 ` Daniel P. Berrange [this message]
2017-01-30 13:59 ` [Qemu-devel] [PATCH v4 0/8] Switch all subdirs over to modular trace.h file 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=20170125161417.31949-9-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --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 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 NNTP newsgroup(s).