![]() Chapter Contents |
![]() Previous |
![]() Next |
SAS/C Software: Changes and Enhancements, Release 6.50 |
In Release 6.50, the compiler allows for the placement of the debugging information in the object
file when the
dbgobj
option is specified. The
dbgobj
option is specified by default when the
autoinst
option is enabled. When this information is discovered by COOL to be present in the object file, COOL will write the debugging information to
a file supported
by the debugger. The default filename used is somewhat different than when the debugging information is written directly by the compiler in that it is generated using the sname of the
containing object.
The
dbglib
option specifies a debugger file qualifier that provides for customization of the destination of the debugger file.
For each
platform,
dbglib
specifies something different:
sname
)./
', then it is assumed that this is either a '
//sf:
' file specification or an SFS path. In this case, the specification is prepended to the filename. For example,
will generate the namedbglib(//sf:ted/)
If the option specified does not start with a '//sf:/ted/sname.DB
/
' then it is considered to be a filemode, and will be appended to the filename. For example,
will generate the namedbglib(d2)
sname.db.d2
will generate a filename ofdbglib(/u/sasc/dbg/)
/u/sasc/dbg/sname.dbg370
The option has different defaults on the various platforms:
dbglib(ddn:sysdblib)
dbglib(A)
dbglib()
For the various platforms, the default filename has different forms:
ddn:sysdblib(sname)
sname.DB.A
hfs:sname.dbg370
Note: On OE and UNIX platforms, the sname
is capitalized and remains so for debugger filename generation.
The short form of this option is
-db
.
![]() Chapter Contents |
![]() Previous |
![]() Next |
![]() Top of Page |
Copyright © Mon Mar 9 09:11:22 EST 1998 by SAS Institute Inc., Cary, NC, USA. All rights reserved.