Thanks for the responses. I had forgotten that SIGABRT==abort() which means I have to get the core file to get to the root cause. To date the only information I have is a shell exit status of 134 which from the bash man pages means it died due to SIGABRT. David Ahern On 12/12/2009 01:52 AM, Stefan Weil wrote: > David S. Ahern schrieb: >> I realize this is a rather generic question, but what are typical >> reasons Qemu would be killed by a SIGABRT? I am seeing this on a >> somewhat regular (though not repeatable on demand) basis. I do not have >> a core file, though I hope to capture one if I can get it repeat again. >> >> Thanks, >> > > Look for "abort" in QEMU's code to see the possible reasons. > > In many cases, the reason will be printed to stderr before > aborting. Did you call QEMU from a console and get some > output there? Or maybe the stderr output went into a file? > > Run "ulimit -c unlimited" before you run QEMU, then a > core file will be written automatically on SIGABRT. > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
