> On 05 Aug 2015, at 19:56, Paolo Bonzini <pbonz...@redhat.com> wrote: > > ... I am not sure why things break for Stefan...
I confirm Stefan's conclusion, neither in my configuration adding #include "qemu-common.h" ... in cpu-exec.c makes any difference. however adding: #if defined(_WIN64) #ifdef sigsetjmp #undef sigsetjmp #endif #define sigsetjmp(env, savesigs) _setjmp(env, NULL) #endif ... fixes the problem, my custom QEMU happily blinks the LEDs on Win 8.1 64-bits (see below). perhaps a headers check would be helpful, such mysterious behaviours usually back fire at a certain point. regards, Liviu GNU ARM Eclipse 64-bits QEMU v2.3.50 (qemu-system-gnuarmeclipse.exe). Board: 'STM32F4-Discovery' (ST Discovery kit for STM32F407/417 lines). Device: 'STM32F407VG' (Cortex-M4 r0p0, MPU), Flash: 1024 kB, RAM: 128 kB. Command line: 'f4' (2 bytes). Cortex-M4 r0p0 core initialised. GDB Server listening on: 'tcp::1234'... Cortex-M4 r0p0 core reset. ... connection accepted from 127.0.0.1. PRIGROUP unimplemented Execute 'mon system_reset'. Cortex-M4 r0p0 core reset. main(argc=1, argv=["f4"]); Hello ARM World! System clock: 168000000Hz Standard output message. Standard error message. [Green LED On] [Green LED Off] Second 1 [Green LED On] [Green LED Off] Second 2 [Green LED On] [Green LED Off] Second 3 [Green LED On] [Green LED Off] Second 4 [Green LED On] [Green LED Off] Second 5 QEMU exit(0)