Solaris 2.6.5 panic when trying to debug a binary with Sun Workshop V5n1, or V6n1 debugger

Host environment

• Operating system: Linux
• OS/kernel version: Lubuntu 20.04 LTS / 5.15.0-88-generic
• Architecture: x86-64/AMD64
• QEMU flavor: qemu-system-sparc
• QEMU version: 8.0.5, 8.2.0rc4, master 8.2.50 (v8.2.0-196-g7425b627)
• QEMU command line: -machine SS-5 -cpu "Fujitsu MB86904" -m size=256M -vga tcx -g 1024x768x8 -drive file=sparc.qcow2,bus=0,unit=0,media=disk,format=qcow2,id=hd0 -boot d -prom-env "auto-boot?=false"

Emulated/Virtualized environment

• Operating system: Solaris 2.6.5
• OS/kernel version: SunOS sunsol 5.6 Generic_105181-39 sun4m sparc SUNW,SPARCstation-5
• Architecture: Sun4m

Description of problem

Following this guide, and similarly to issue #1166 (closed), the guest panics when one tries to debug a binary with the debugger provided in Sun Workshop V5n1, and in Sun Workshop v6n1 as well. The Sun Workshop is EOL, available at the archive, with free non-expiring demo licenses made available by Sun before the Oracle acquisition. The guest was patched with the latest available patches included in this cluster. The following information was collected when debugging bunzip2, but any binary panics the guest.

panic: Non-parity synchronous error: ctx=54 va=ef7cbc44 pa=e0a8c44
syncing filesystems... 15 done
NOTICE: zs3:ring buffer overflow

Steps to reproduce

1. Start the Sun Workshop (SUNWspro/bin/workshop), go to the Debugger in the menu
2. Debug/New Program, load any binary, place a breakpoint in main or wherever
3. Execute, guest kernel panic

Additional information

This happens with the Fujitsu MB86904 specified as CPU, and without specifying a cpu, using the default for the SS-5.

Explicitly setting the TI MicroSparc I and setting memory to 32M seems to start the debugger, the guest still panics, but a bit further down the line