Thanks Peter for this information!
I guess our code was tweaked to run with this options a long time ago -
so I will have to do some investigations to get it working with a valid
NVIC...
As of writing I remember having a similar issue some time ago (which I now
found to have resulted in Bug 1636126).
Sorry for not remembering this before!
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1738202
Title:
qemu 2.11 segfaults on elf file that worked with qemu2.7
Status in QEMU:
Invalid
Bug description:
running on cygwin in Windows 7
QEMU 2.10.93 segfaults:
$ /opt/qemu2.11/qemu-system-arm -M integratorcp -cpu cortex-m4 -semihosting
-nographic -monitor null -serial null -no-reboot -kernel
MFWso_Cycle_f1uP2_CUNIT_0.elf
Segmentation fault
where QEMU 2.7.0 worked:
$ /opt/qemu2.7/qemu-system-arm -M integratorcp -cpu cortex-m4 -semihosting
-nographic -monitor null -serial null -no-reboot -kernel
MFWso_Cycle_f1uP2_CUNIT_0.elf
------------ CUnit_MFWso_Cycle_f1 ------------
CUnit - A Unit testing framework for C - Version 2.1-0
http://cunit.sourceforge.net/
Suite: Suite_MFWso_Cycle_f1
Test: MFWso_Cycle_f1() ... passed
Test: MFWso_GetPhysicalStateData() ... passed
Test: MFWso_GetOutputData() ... passed
Test: MFWso_GetSafeChannelOK() ... passed
--Run Summary: Type Total Ran Passed Failed
suites 1 1 n/a 0
tests 4 4 4 0
asserts 54 54 54 0
----------------------------------------
Omitting the -cpu parameter results (for both versions) to hang of
qemu (no output, no end, full cpu load).
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1738202/+subscriptions
