diff options
Diffstat (limited to 'results/classifier/118/graphic/1738202')
| -rw-r--r-- | results/classifier/118/graphic/1738202 | 80 |
1 files changed, 80 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1738202 b/results/classifier/118/graphic/1738202 new file mode 100644 index 00000000..3277b044 --- /dev/null +++ b/results/classifier/118/graphic/1738202 @@ -0,0 +1,80 @@ +graphic: 0.882 +peripherals: 0.842 +architecture: 0.794 +performance: 0.780 +files: 0.770 +semantic: 0.759 +register: 0.756 +socket: 0.755 +permissions: 0.739 +debug: 0.739 +device: 0.705 +ppc: 0.699 +network: 0.693 +PID: 0.677 +hypervisor: 0.673 +arm: 0.651 +mistranslation: 0.644 +assembly: 0.640 +vnc: 0.623 +boot: 0.607 +virtual: 0.575 +TCG: 0.569 +user-level: 0.568 +risc-v: 0.554 +kernel: 0.548 +x86: 0.534 +VMM: 0.483 +KVM: 0.449 +i386: 0.332 + +qemu 2.11 segfaults on elf file that worked with qemu2.7 + +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). + + + +Your command line is badly broken: "-M integratorcp" requests a model of an integratorcp board, but "-cpu cortex-m4" tries to put an M-profile CPU in it, which is not something that board can support. In particular the resulting system model will have no NVIC in it. This only worked by accident in previous versions of QEMU. + +Ideally we should have better cpu-model compatibility checking in the board models, in which case we could print a message saying "CPU type cortex-m4 is not compatible with the integratorcp board" rather than crashing. + +If you omit -cpu you'll get the default CPU type for the board, which is an arm926. That's a sensible board+cpu combination but presumably your guest code is not built to run on that hardware, which will be why it just falls over. ("QEMU prints no output" often means "guest code has crashed or gone into an infinite loop", rather than a QEMU bug.) + +If your code needs to run on an M-profile CPU then you'll need to pick one of the M-profile board models. As of 2.11 those are lm3s6965evb, lm3s811evb, mps2-an385, mps2-an511, netduino2. + + +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! + |