* [Bug 1910540] [NEW] where the trace file "trace-*"
@ 2021-01-07 13:04 xiangjzh
2021-05-12 12:00 ` [Bug 1910540] " Stefan Hajnoczi
2021-05-12 15:02 ` Thomas Huth
0 siblings, 2 replies; 3+ messages in thread
From: xiangjzh @ 2021-01-07 13:04 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
I compile qemu-system-aarch64 with --enable-trace-backends=simple
option, then start qemu with -trace nvme* , qemu start successful but I
cann't find the trace file "trace-*" at qemu started directory.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910540
Title:
where the trace file "trace-*"
Status in QEMU:
New
Bug description:
I compile qemu-system-aarch64 with --enable-trace-backends=simple
option, then start qemu with -trace nvme* , qemu start successful but
I cann't find the trace file "trace-*" at qemu started directory.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1910540/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 1910540] Re: where the trace file "trace-*"
2021-01-07 13:04 [Bug 1910540] [NEW] where the trace file "trace-*" xiangjzh
@ 2021-05-12 12:00 ` Stefan Hajnoczi
2021-05-12 15:02 ` Thomas Huth
1 sibling, 0 replies; 3+ messages in thread
From: Stefan Hajnoczi @ 2021-05-12 12:00 UTC (permalink / raw)
To: qemu-devel
I tested qemu.git/master on Linux x86_64 to confirm that the simple
trace backend works. trace-$pid files are written to the current working
directory.
If QEMU prints a warning that the trace event name does not exist, try
escaping the asterisk on your command-line: -trace nvme\*
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910540
Title:
where the trace file "trace-*"
Status in QEMU:
New
Bug description:
I compile qemu-system-aarch64 with --enable-trace-backends=simple
option, then start qemu with -trace nvme* , qemu start successful but
I cann't find the trace file "trace-*" at qemu started directory.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1910540/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 1910540] Re: where the trace file "trace-*"
2021-01-07 13:04 [Bug 1910540] [NEW] where the trace file "trace-*" xiangjzh
2021-05-12 12:00 ` [Bug 1910540] " Stefan Hajnoczi
@ 2021-05-12 15:02 ` Thomas Huth
1 sibling, 0 replies; 3+ messages in thread
From: Thomas Huth @ 2021-05-12 15:02 UTC (permalink / raw)
To: qemu-devel
You can find the trace-event files in the source tree, if you were
talking about those. Anyway, this does not really sound like a bug, so
I'm closing this ticket now. If you need general help, please use the
qemu-discuss mailing list or the #qemu channel on OFTC IRC instead.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910540
Title:
where the trace file "trace-*"
Status in QEMU:
Invalid
Bug description:
I compile qemu-system-aarch64 with --enable-trace-backends=simple
option, then start qemu with -trace nvme* , qemu start successful but
I cann't find the trace file "trace-*" at qemu started directory.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1910540/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-05-12 15:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-07 13:04 [Bug 1910540] [NEW] where the trace file "trace-*" xiangjzh
2021-05-12 12:00 ` [Bug 1910540] " Stefan Hajnoczi
2021-05-12 15:02 ` Thomas Huth
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.