Closed
Bug 85979
Opened 23 years ago
Closed 23 years ago
Always use the -xs compiler option in Solaris debug builds.
Categories
(NSPR :: NSPR, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
4.2
People
(Reporter: wtc, Assigned: wtc)
Details
Attachments
(1 file)
585 bytes,
patch
|
Details | Diff | Splinter Review |
Right now we only use the -xs compiler option in Solaris debug builds when we are making a binary release (i.e., if BUILD_NUMBER is set). In the new world, compiler options are set by the configure script. We would need to add a configure option to indicate we are making a binary release. I think that's too much trouble. So I am just going to always use -xs for Solaris debug builds. Here is the documentation of the -xs compiler option. -xs Disables Auto-Read for dbx. Use this option in case you cannot keep the .o files around. It passes the -s option to the assembler. No Auto-Read is the older way of loading symbol tables. It places all symbol tables for dbx in the executable file. The linker links more slowly and dbx initializes more slowly. Auto-Read is the newer and default way of loading sym- bol tables. With Auto-Read, the information is distri- buted in the .o files, so that dbx loads the symbol table information only if and when it is needed. Hence, the linker links faster, and dbx initializes faster. With -xs, if you move the executables to another direc- tory, then to use dbx, you can ignore the object (.o) files. Without -xs, if you move the executables, you must move both the source files and the object (.o) files, or set the path with the dbx pathmap or use command.
Assignee | ||
Comment 1•23 years ago
|
||
Assignee | ||
Comment 2•23 years ago
|
||
I checked in the patch on the trunk of NSPR.
Status: NEW → RESOLVED
Closed: 23 years ago
Priority: -- → P2
Resolution: --- → FIXED
Target Milestone: --- → 4.2
You need to log in
before you can comment on or make changes to this bug.
Description
•