qemu-e2k/scripts
Stefan Hajnoczi 913540a376 trace: allow PRI*64 at beginning and ending of format string
The tracetool parser only picks up PRI*64 and other format string macros
when enclosed between double quoted strings.  Lift this restriction by
extracting everything after the closing ')' as the format string:

  cpu_set_apic_base(uint64_t val) "%016"PRIx64
                                  ^^        ^^

One trick here: it turns out that backslashes in the format string like
"\n" were being interpreted by echo(1).  Fix this by using the POSIX
printf(1) command instead.  Although it normally does not make sense to
include backslashes in trace event format strings, an injected newline
causes tracetool to emit a broken header file and I want to eliminate
cases where broken output is emitted, even if the input was bad.

Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-09-17 15:14:05 +00:00
..
checkpatch.pl
create_config
feature_to_c.sh
get_maintainer.pl
hxtool
make_device_config.sh
ordereddict.py
qapi-commands.py
qapi-types.py
qapi-visit.py
qapi.py
qemu-binfmt-conf.sh
refresh-pxe-roms.sh
signrom.sh
simpletrace.py
texi2pod.pl
tracetool trace: allow PRI*64 at beginning and ending of format string 2011-09-17 15:14:05 +00:00
update-linux-headers.sh