On 09/06/2013 12:50 AM, Anthony Liguori wrote:
On Thu, Sep 5, 2013 at 7:20 AM, Michal Novotny minov...@redhat.com wrote:
This is the patch to introduce SIGILL handler to be able to trigger
SIGSEGV signal in qemu. This has been written to help debugging
state when qemu crashes by SIGSEGV as a
Il 05/09/2013 14:19, Michal Novotny ha scritto:
This is the patch to introduce SIGILL handler to be able to trigger
SIGSEGV signal in qemu. This has been written to help debugging
state when qemu crashes by SIGSEGV as a simple reproducer to
emulate such situation in case of need.
What's wrong
On 09/05/13 15:26, Paolo Bonzini wrote:
Il 05/09/2013 14:19, Michal Novotny ha scritto:
This is the patch to introduce SIGILL handler to be able to trigger
SIGSEGV signal in qemu. This has been written to help debugging
state when qemu crashes by SIGSEGV as a simple reproducer to
emulate such
On 09/05/2013 04:50 PM, Anthony Liguori wrote:
+int *p = NULL;
+
+*p = 0xDEADBEEF;
I won't repeat the questions from Paolo and Lazlo (I share their
confusion) but will simply add that you cannot rely on NULL address
accessing causing a SEGV. Even with all the use of volatile in
On Thu, Sep 5, 2013 at 7:20 AM, Michal Novotny minov...@redhat.com wrote:
This is the patch to introduce SIGILL handler to be able to trigger
SIGSEGV signal in qemu. This has been written to help debugging
state when qemu crashes by SIGSEGV as a simple reproducer to
emulate such situation in
