Seiji Aguchi 5e2ac51917 add timestamp to error_report() ... [Issue] When we offer a customer support service and a problem happens in a customer's system, we try to understand the problem by comparing what the customer reports with message logs of the customer's system. In this case, we often need to know when the problem happens. But, currently, there is no timestamp in qemu's error messages. Therefore, we may not be able to understand the problem based on error messages. [Solution] Add a timestamp to qemu's error message logged by error_report() with g_time_val_to_iso8601(). Signed-off-by: Seiji Aguchi <seiji.aguchi@hds.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>		2013-07-10 13:42:09 -04:00
..
acl.c
aes.c
bitmap.c
bitops.c
cache-utils.c
compatfd.c
crc32c.c
cutils.c
envlist.c
error.c
event_notifier-posix.c
event_notifier-win32.c
fifo8.c
hbitmap.c
hexdump.c
host-utils.c
iov.c
Makefile.objs
module.c
notify.c
osdep.c
oslib-posix.c
oslib-win32.c
path.c
qemu-config.c
qemu-error.c	add timestamp to error_report()	2013-07-10 13:42:09 -04:00
qemu-openpty.c
qemu-option.c
qemu-progress.c
qemu-sockets.c
qemu-thread-posix.c
qemu-thread-win32.c
qemu-timer-common.c
unicode.c
uri.c