Issues While Running Debugger

The following issues involve the kernel debugger.

SPARC: Problems With dbx Debugger While Processing 64-bit Objects (6347707)

The dbx debugger terminates with a memory access failure while processing certain 64-bit executable files and libraries. However, the problem does not affect the normal use of these 64-bit objects. An error message similar to the following example is displayed:

dbx: internal error: signal SIGBUS (invalid address alignment)

Workaround: Use either the mdb debugger or the Solaris Dynamic Tracing facility instead. These alternatives can diagnose processes that use the 64-bit objects.

System Might Loop When Master CPU Is Changed (4405263)

A system that is running the Solaris kernel debugger to debug a live system might loop with incomplete error messages. This loop occurs when the OpenBoot PROM's master CPU is changed. A system reset restores the system to operation. However, the traces of the original failure are lost. Consequently, you cannot perform a diagnosis of the fatal reset.

Workaround: When the system is at the PROM level, the OpenBoot's ok prompt is displayed. In a system with multiple CPUs, the ok prompt is preceded by a number that is enclosed in curly braces. This number indicates the active CPU in the system. To run your debug session while at the PROM level, use the following steps.

1. Raise pil to f by typing the following command:

   {0} ok h# 0f pil!

2. Use the switch-cpu command to selectively switch from the currently active CPU to different CPUs. For example, to switch from CPU #0 to CPU #1, type the following command:

   (0) ok 1 switch-cpu

   The ok prompt is now preceded by the number of the CPU to which you switched.

   {1} ok

3. Run your debugger.

4. At the end of your debugger session, issue a reset-all command to return the system to normal use.