From: Stefan Hajnoczi <stefanha@gmail.com>
To: Derrick McKee <derrick.mckee@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU simpletrace.py
Date: Mon, 4 Sep 2017 10:22:20 +0100 [thread overview]
Message-ID: <20170904092220.GC20713@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAJoBWHxiBU9bc-GMOxc9n=U6r3xbWQ=b7aeU0p5afhHZzm4RcA@mail.gmail.com>
On Fri, Sep 01, 2017 at 03:52:03PM +0000, Derrick McKee wrote:
> I am having trouble using the simpleparser.py script in QEMU. Hopefully, I
> am doing something incorrect and you can quickly set me back on course.
>
> I have generated a trace file as per the instructions in
> docs/devel/tracing.txt. However, whenever I try to run the simpleparser.py
> script I get a file not found error:
>
> <QEMU source>/build/scripts/simpletrace.py trace-events-all trace-30218
> Traceback (most recent call last):
> File "/home/derrick/code/qemu/build/scripts/simpletrace.py", line 262, in
> <module>
> run(Formatter())
> File "/home/derrick/code/qemu/build/scripts/simpletrace.py", line 236, in
> run
> events = read_events(open(sys.argv[1], 'r'))
> IOError: [Errno 2] No such file or directory: 'trace-events-all'
>
> It seems like the python script is considering 'trace-events-all' as a
> file, but the directions don't make it seem like it should be a file.
trace-events-all is a file that is generated at build time. It is
needed by simpletrace.py.
You can find the trace-events-all file in the root directory of your
QEMU build tree.
The documentation says:
The individual "trace-events" files are merged into a "trace-events-all" file,
which is also installed into "/usr/share/qemu" with the name "trace-events".
If you can think of a way to make the documentation clearer, please feel
free to send a patch. Guidelines on submitting patches are here:
https://wiki.qemu.org/index.php/Contribute/SubmitAPatch
Stefan
prev parent reply other threads:[~2017-09-04 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 15:52 [Qemu-devel] QEMU simpletrace.py Derrick McKee
2017-09-04 9:22 ` Stefan Hajnoczi [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=20170904092220.GC20713@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=derrick.mckee@gmail.com \
--cc=qemu-devel@nongnu.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 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).