aboutsummaryrefslogtreecommitdiff
path: root/target-ppc/translate_init.c
diff options
context:
space:
mode:
authorSeiji Aguchi <seiji.aguchi@hds.com>2013-07-03 23:02:46 -0400
committerLuiz Capitulino <lcapitulino@redhat.com>2013-07-10 13:42:09 -0400
commit5e2ac5191772dea782ff78e95edd395985273019 (patch)
tree804bd99545123456168886337c520707bd77ea2b /target-ppc/translate_init.c
parentf53cae50f81449596e55159cfe61efbef9246b2e (diff)
downloadqemu-arm-5e2ac5191772dea782ff78e95edd395985273019.tar.gz
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>
Diffstat (limited to 'target-ppc/translate_init.c')
0 files changed, 0 insertions, 0 deletions