Chapter 3 Late-Breaking Solaris Runtime Issues

This chapter describes known runtime problems. You may also want to refer to the online runtime_bugs file in the SUNWrdm package on the Solaris 7 3/99 CD for additional runtime problems.

The information in this chapter supplements any information listed in the runtime_bugs file that is part of the SUNWrdm package on the Solaris 7 3/99 CD. If you boot from the Solaris 7 3/99 CD, the runtime_bugs file is located in the directory:

/cdrom/sol_7_399_sparc/s0/Solaris_2.7/Docs/release_info/C

The default installed location for the runtime_bugs file is the directory:

/usr/share/release_info/Solaris_2.7/C

The name of this product is Solaris 7 but code and path or package path names may use Solaris 2.7 or SunOS 5.7. Always follow the code or path as it is written.

64-Bit Solaris Bugs

krtld Does Not Recognize sparcv9 Register Symbols (4203394)

When loading an unbundled device driver, STREAMS module, file system, or other kernel module, you may see the following error message:

kernel_module_path: undefined symbol
WARNING: mod_load: cannot load module 'kernel_module_path'

The kernel runtime linker does not recognize the new register symbol type introduced in the SC5.0 FCS compilers and assemblers for 64-bit SPARC binaries.

Workaround: You must verify that the error message was generated because the kernel runtime linker does not recognize the new register symbol type. To do this, type:

# nm kernel_module_path | grep REGI

If this is the problem, the output from this command is a table that shows one row with 2 in the Value column and REGI in the Type column and another row with 3 in the Value column and REGI in the Type column. An example is:

[154]   |             2|           0|REGI |GLOB |0    |UNDEF  |
[155]   |             3|           0|REGI |GLOB |0    |UNDEF  |

To correct the problem:

• If you have the source code for the kernel module, recompile the kernel module with -xregs=no%appl option, or, if it is written in assembly language, assemble it with -xregsym=no option.

• If you do not have the source code, contact the provider of the kernel module to report the problem.

Debugging

dbx 4.0 Cannot Dump the Stack Trace When Debugging a Multi-Threaded Program (4207409)

When debugging a multi-threaded program with a signal handler on a given thread stack, dbx 4.0 cannot successfully dump the thread's stack.

Workaround: Use dbx 5.0.