id = 2059
title = "Solaris 2.6.5 panic when trying to debug a binary with Sun Workshop V5n1, or V6n1 debugger"
state = "closed"
created_at = "2023-12-28T08:23:00.133Z"
closed_at = "2024-04-14T12:07:21.921Z"
labels = ["Closed::Fixed", "target: sparc"]
url = "https://gitlab.com/qemu-project/qemu/-/issues/2059"
host-os = "Linux"
host-arch = "x86-64/AMD64"
qemu-version = "8.0.5, 8.2.0rc4, master 8.2.50 (v8.2.0-196-g7425b6277f)"
guest-os = "Solaris 2.6.5"
guest-arch = "Sun4m"
description = """Following [this guide](https://www.gekk.info/articles/solaris26.htm), and similarly to issue #1166, the guest panics when one tries to debug a binary with the debugger provided in [Sun Workshop V5n1](https://archive.org/details/sunworkshopforsolaris2vol5num1_704546810revb), and in [Sun Workshop v6n1](https://archive.org/details/devpro_v6n1) as well.
The Sun Workshop is EOL, available at the archive, with free non-expiring demo licenses [made available](https://archive.org/details/suncomp-lic) by Sun before the Oracle acquisition.
The guest was patched with the latest available patches included [in this cluster](https://archive.org/details/sun26gnu).
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
```"""
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 = """This happens with the Fujitsu MB86904 specified as CPU, and without specifying a cpu, using the default for the SS-5.

![sol26](/uploads/375b25f8614a49bfe634c71520890b5c/sol26.png)

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

![sol262](/uploads/7a9c834f66fea1706ef92eb65ce8fe39/sol262.png)"""