Chapter 2
Fixed Problem Summary


Problems Fixed in the V4.6.0 Release


Base Operating System

23762
Messages indicating that a device needed to be cleaned were not logged in ktlog.
23789
The -G option to useradd/usermod issued a warning message when the default group was duplicated.
230703
Core dumps were not recorded in ktlog.
234196
dumpconf needed a -t option to show temporary names.
234549
tar sometimes exited with an incorrect code.
236186
Binary executables with mode 2700 could not be executed.
237577
The uncompress command failed with SEGV when trying to uncompress a corrupt .Z file.
237942
The diskid command displayed a misleading warning when it was run by a user not having root permissions.
239122
The operating system no longer needed I/O alignment restrictions.
241061
make did not handle macro recursion properly in substitutions.
241612
Warning messages flooded the console if an FC Host Adapter failed its initializaton.
242591
Invalid times appeared in the EES log during system boot.
243557
mount -v dumped core if several EFS mount options were specified.
243677
standload displayed a confusing message when autoBoot was either not set or set to 0x0.
243809
ptx/ADMIN could not compile a MFG kernel.
244061
make incorrectly reported too many command lines.
244307
The swap output and man page did not explain the "wasted pages" reported by the -f option.
245031
The make(1) man page did not describe limitations when using macros.
245144
mailx did not send a message non-interactively if the TERM variable was invalid.
245405
The devctl -d command took too long on an FC JBOD device.
245646
A problem with a sar function caused the utility to dump core.
246067
The printf command did not support C constants.
246282
When df -k was run on a disk device, it reported status for all filesystems.
246367
tar -cf did not truncate the file to which it was writing.
246517
tar did not extract modification times for directories.
246533
make rebuilt target objects if ar was called within the makefile and the filename was over 16 characters long.
246580
The command ps -p pid returned an incorrect exit status if the pid did not exist.
247127
A memory leak and an errno problem existed in libnsl.
247180
The rm(1) man page was unclear about the use of the -i option.
247206
grep -E did not handle the | special character correctly.
247242
There was a performance problem in the System V message queue subsystem.
247885
initgroups() wrote a message to standard error when a user was in too many groups.
248900
df failed when run on files larger than 2 GB.
248999
The regcomp() routine dumped core when processing a valid expression string.
249050
compress did not work with the - option.
249119
The sched deamon's process startup time was incorrect.
249193
fsck printed an incorrect error message.
249403
A problem in the mdc driver caused the system to panic.
249555
The egrep man page stated that lines are limited to BUFSIZ characters; however, they are limited to LINE_MAX characters.
249923
savecore did not assign execute permissions to the crash files it saved.
249983
Zombie processes were not listed as <defunct> in the output from ps -ef.
250240
The realpath() routine did not work properly for a file in the root directory.
250287
The uptime(1) man page defined "load average" incorrectly.
250320
A problem in a streams routine caused the system to panic.
250348
awk dumped core when attempting to process lines containing 512 or more characters.
250446
The base component of ptx/PDC generated confusing error messages.
250447
The monitor command displayed incorrect memory values for regions.
250478
Front panel operations needed to be moved from disk driver routines.
250479
The script used by umask did not specify a complete path for the basename command.
250587
A multithreaded application invoking the ioctl FIONBIO or FIOASYNC on a BSD socket could trigger unpredictable behavior on the socket and eventually panic the system.
250605
An hdsinfo(1) man page was needed.
250627
The groupadd command did not use the C_MAXUID kernel variable to determine the maximum GID possible on the system.
250628
The useradd command did not use the C_MAXUID kernel variable to determine the maximum UID possible on the system.
250630
A problem with the boot loader could cause a system boot to fail.
250637
usleep did not handle the granularity of timer values correctly.
250642
The proc_ctl(2SEQ) man page did not describe the PROC_RELINQUISH and PROC_OPENT commands.
250664
asm longlong support was no longer needed in config.
250740
A problem with regions and virtual memory caused the system to panic.
250751
A threads component was needed to collect threads metrics.
250864
The single mem_wait semaphore needed to be replaced with a mem_wait semaphore per quad.
250929
The type dnlc_t was not defined in dnlc.h.
250961
Failed su login attempts could cause the umask to change to 0377.
250968
If a zombie process existed in the background, the system panicked when uadmin 2 0 was executed.
250988
nawk dumped core when printing a line longer than 20 KB.
251039
The debugger attempted to stop an LWP in the zombie state, causing the system to panic.
251229
The delay time between FLOGI retries was inconsistent.
251282
The shells(4) man page did not describe the addusr.def file.
251341
A problem in the mdc driver caused the system to deadlock.
251384
The diskid command failed when a device was specified with a partition name.
251409
The printf command dumped core when %n was used as a format string.
251411
The printf command did not handle variable field_width formats.
251422
The fdiv_stats command incorrectly represented the result of an lseek64 as an int.
251442
A race between devctl operations caused the system to panic.
251461
A race in the kernel caused the system to panic.
251472
The streams queue allocation and deallocation code needed some fixes.
251501
truss reported improper values in hexadecimal instead of octal.
251516
cpio failed when a scratch installation was performed from an EFS root filesystem to another disk.
251517
The default console definition did not work with ptx/ADMIN.
251519
The ptx/ADMIN "Terminal type" menu was confusing.
251534
savecore did not log an error message when there was not enough room in /usr/crash to save a memory dump.
251564
A race condition in the mdc driver caused the system to panic.
251603
Pass-through ioctls sent Unit Attention messages to ktlog.
251609
When a per-quad dumplist was created with ptx/ADMIN, the /etc/dumplist file was not updated correctly.
251655
Some macros in the mc_param.h file did not expand properly during use.
251670
The fabric and scsibus drivers did not set status properly when certain errors were returned.
251692
A streams routine allocated an incorrectly-sized buffer.
251881
The number of ncache blocks in the system could not be increased dynamically.
251898
A sysi86 command returned an incorrect error when a copyout() failed.
251904
A typo in the ibms36d.geom file prevented a VTOC from being created.
251923
diff is very slow.
251935
A race in virtual memory could cause the system to panic.
251973
$LOGNAME and $TERM were set incorrectly when su - name was run and the user name contained more than 11 characters.
251979
The obsolete configuration option P_LOCK_DEBUG needed to be removed.
251980
The command cal year did not always display properly for multibyte locales.
252014
In the sync_op() routine, SYNC_POSTVEC did not sleep interruptably when it allocated memory.
252027
In the sync_op() routine, SYNC_POST did not honor the SYNCF_URGENT flag.
252072
Support was needed for the FIONREAD, FIONBIO, FIOASYNC, FIOSETOWN, and FIOGETOWN ioctls.
252088
The p_flag field in the proc structure could become corrupted and cause the system to panic.
252101
The mpt driver did not reintegrate disks properly.
252108
When a data object was relocated, another symbol referring to the same object was left pointing to the original location in the shared library.
252126
A problem with the mpt driver caused the system to panic.
252140
A problem in an internal routine caused the system to panic with the message trap: exception integer divide by zero.
252144
A problem in the tli module caused the system to panic.
252163
A problem with a semaphore routine caused the system to panic with an MMU fault.
252206
The localedef command did not parse white space correctly.
252222
A problem that occurred when migrating multithreaded processes caused the system to panic.
252412
ptx/TCP/IP drivers were not notified when a device name was changed with devctl -n.
252449
The rc1 script ran the shutdown scripts in stand-alone mode.
252455
The process component for ptx/PDC used too much CPU when doing lookups in /etc/passwd.
252469
When lwp_trace() transferred data, it used 4096 as the minimum block size, which could overwrite a buffer and cause a core dump.
252496
lwp_trace() used 4096 as the block size when the user requested a size greater than 4096.
252498
infodev did not display Node and Port WWN information for FC Host Adapters.
252614
A problem with the mpt driver could cause the system to panic.
252650
devctl -c operations failed for new disks in the upper half of the boot Pbay.
252751
A problem with an ff internal function caused the system to panic.
252911
When a route was restored, the message sdX(port Y): resuming route was not logged.
252979
The obsolete P_LOCK_DEBUG configuration option needed to be removed.
253022
The ff driver did not log internal errors from the FC Host Adapter.
253616
The showcfg command did not always display the boot name correctly.
253828
awk/oawk did not set uninitialized fields.

ptx/C and Programming Tools

241790
cprs did not support nesting for structures or classes.
246794
lint issued an incorrect warning about an unsigned comparison against zero.
247814
ar did not warn about certain archive format problems.
249202
ld created a global object instead of using the weak symbol in a shared object.
249465
When the debug create command was used, processes were stopped after the exec system call.
250077
A problem in the compiler caused an invalid warning message.
251169
dis crashed when the -d option was used.
251317
The ar(1) man page incorrectly stated that filenames were limited to 14 characters.
251318
The m4(1) man page needed clarification regarding the use of options.
251518
nm -u -r produced incorrect output when run on libraries.
251793
The -W0,-B option was not documented in the cc(1) man page.
251925
The example in the lex(1) man page was incorrect.
252154
The preprocessor generated unnecessary warnings for LL and ULL suffixes.
252325
cxref did not truncate lines when -wnum was specified.
252326
cxref did not handle -- correctly on the command line.
252327
cxref did not continue to parse the command line after an error occurred.
252328
m4 used the wrong precedence for ~ and !.
252329
m4 did not always handle output redirection correctly.
252330
The m4 macro m4wrap did not work correctly.
252323
The cflow command printed garbage on the first line of output.
252324
cflow did not handle -- on the command line.
252331
m4 did not allow space between the -D and -U flags and their arguments.
252332
m4 did not return from option processing when it encountered -- on the command line.
252338
ar did not parse the command line correctly if an argument began with a dash.
252341
m4 did not continue to process arguments if one argument failed.
252354
tsort failed when -- was specified on the command line.
252474
The compiler did not report a write failure when the filesystem was full.
253013
The ngen short block counter overflowed when large binaries were compiled.

edb Debugger

240611 [3155]
edb required a full path for a source file.
245722 [3700]
Running a job silently killed already running jobs.
249748 [4266]
edb issued a warning if a core file did not match the specified executable.
249868 [4289]
edb could not set a break on an unmangled C++ function name.
250646 [4414]
edb lost scope after a process completed.
250647 [4415]
An edb step after watchpoint stopped at the same line again.
250659 [4421]
The register window displayed incorrect floating point values.
250910 [4498]
The edb call command did not handle arrays as actual arguments.
250912 [4497]
An edb call to a floating point function did not pop the floating point stack.
250913 [4496]
The edb call command did not handle functions that return structures.
250920 [4494]
Limitations to the edb call command needed to be documented.
252336 [4826]
edb failed to read datatypes larger than 4 KB.
252459 [4843]
The edb call command could not handle a generic C++ function in another source file.
253036 [4929]
A wraplines option was needed to turn off line wraps in the edb output.