blob: b4326ee2bf283f4b2b709ef129ecfb4081e50c78 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
kernel: 0.946
network: 0.913
graphic: 0.909
device: 0.896
boot: 0.892
vnc: 0.833
virtual: 0.798
peripherals: 0.789
socket: 0.770
user-level: 0.718
architecture: 0.706
PID: 0.691
files: 0.690
permissions: 0.585
semantic: 0.547
debug: 0.545
VMM: 0.522
performance: 0.514
register: 0.454
x86: 0.434
ppc: 0.407
TCG: 0.364
mistranslation: 0.327
risc-v: 0.297
hypervisor: 0.290
arm: 0.286
i386: 0.282
KVM: 0.079
assembly: 0.063
qemu-system-m68k segfaults on opcode 0x4848
Description of problem:
Running an m68k executable with opcode 0x4848 will segfault qemu-system-m68k
Steps to reproduce:
1. Boot m68k debian
2. Compile program (see above for the oops.c source) that executes opcode 0x4848
3. Run program
4. QEMU segfaults:
```
./debian-m68k.sh: line 10: 4420 Segmentation fault (core dumped) qemu-system-m68k -boot c -M q800 -serial none -serial mon:stdio -m 1000M -net nic,model=dp83932,addr=08:00:07:12:34:89 -net user -append "root=/dev/sda2 rw console=ttyS0 console=tty" -kernel virt/vmlinux-4.16.0-1-m68k -initrd virt/initrd.img-4.16.0-1-m68k -drive file=virt/debian-m68k-deb10.qcow2,format=qcow2 -nographic
```
Additional information:
|