Technical data

signal SEGV (no mapping at the fault address) in main at line 29 in file "test.c"
In this case, when the user types the cont -sig SEGV command to continue execution with the
SEGV signal, dbx displays the warning of the unexpected SIGTRAP.
This bug is introduced into the Solaris 10 OS on x86 platforms when kernel patch 127112 is
installed.
Workaround: Do not install kernel patch 127112. Uninstall the kernel patch if it has already
been installed. For more information about this bug, see the Sun Studio Support News page at
http://developers.sun.com/sunstudio/support/troubleshooting/index.jsp.
SPARC: ProblemsWith dbx DebuggerWhile Processing
64-bit Objects (6347707)
The dbx debugger terminates with a memory access failure while processing certain 64-bit
executable les and libraries. However, the problem does not aect 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 LoopWhen 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
dierent CPUs. For example, to switch from CPU #0 to CPU #1, type the following
command:
Issues While Running Debugger
Chapter 2 • Solaris Runtime Issues 73