Chapter 2
Fixed Problem Summary


Problems Fixed in the V4.5.1 Release


Base Operating System

229395
The /etc/diskid flash option failed if the disk was under ptx/SVM control.
234434
sed and nawk were significantly slower than in previous releases.
235985
The crash p -o command did not work as in previous releases.
239250
The operating system and QCIC firmware did not always negotiate SCSI parameters correctly.
240508
uptime reported invalid information when the system date was set to be earlier than the boot date.
242642
On a scsitape WRITE device, positioning ioctls could write filemarks.
243368
A define was needed for the maximum number of CPUs per quad.
245962
nawk did not handle secondary code sets for certain options.
246142
Support was needed for the dladdr function. See dladdr(3X).
246314
printf did not print minus zero values correctly.
246792
lpadmin -p did not always work correctly.
247324
Additional message queue and semaphore statistics were needed for ptx/PDC.
247619
rgnstat did not display the correct value for the MEM_SHMEM field; rgnctl -ca did not display the status of the region at the next boot; monitor did not display "per-region" values for the Locks Used and % Locks Used fields.
247648
diff -b did not always identify differing lines.
248231
If mv was used on a directory mountpoint that had a different filesystem type from the covered filesystem, CPU stall messages were generated.
248354
VCS disconnect/connect messages were not logged to ktlog.
248565
Messages regarding the cd device appeared in ktlog when the system was booted.
248577
wscanf() sometimes failed.
248814
The mail -F option failed for addresses containing more than 20 characters.
248904
The mpt route-selection routine needed a fix.
249176
Requests for memory could hang.
249222
An auscan routine wrote beyond the end of the directory structure and caused the program to core dump.
249257
truss failed when output was redirected to a file.
249282
monitor displayed incorrect statistics for regions.
249472
devctl -c sometimes left devices with temporary names.
249628
A problem with a mpt routine caused the system to panic.
249713
SIGPIPE was posted for non-FIFO STREAM devices.
249725
truss hung after a traced process exited.
249758
The miniroot did not include the bp command.
249759
The monitor command sometimes exited with a memory fault when it was used to display region information.
249760
A problem in an internal function caused the system to panic.
249815
Native threads and application regions could not be used together.
249817
A UFS filesystem routine could incorrectly report an error and then lose an inode.
249885
The words "load average" were omitted from uptime output.
249964
A cdfs filesystem could not be unmounted.
249984
Zombie processes did not have the correct process credentials.
250038
The crash as command did not work correctly when a process had exited.
250051
Semaphore locking operations took too long.
250069
mpt did not support round-robin route selection.
250100
crontab -e failed with a shell memory fault if a user crontab file did not exist.
250108
nlecho did not display a message in languages other than English.
250111
compress did not handle the -b option properly.
250133
A swapout queue was needed to handle the exiting of the last-in-memory LWP.
250135
The crash u command did not display the correct description; the crash vtop command did not always work correctly.
250136
The uptime(1) man page incorrectly stated that the -u option is supported.
250148
Auditing was not performed correctly for region operations.
250233
A timeout problem caused the system to panic.
250237
libc.so.1 did not contain the _abi_ws* and _abi_wsc* routines present in libc.so.
250269
The flag MPT_DEV_RESET_DONE was no longer needed.
250295
A problem with the scsidisk driver caused a read error.
250314
The core(4) manpage incorrectly stated that the NT_PROCINFO section contains a proc_status_t. The man page should have said that the NT_PROCESSINFO section contains a process_info_t.
250315
When an mptrace()-style debugger such as debug attempted to attach to a multi-threaded process, it failed with EBUSY instead of EACCES.
250426
The STIME column was not formatted properly in ps output.
250432
The system needed the ability to do a single I/O for device-contiguous vectored requests.
250504
Killing a zombie process could cause the system to panic.
250544
Processes with more than one LWP could not migrate across regions.
250561
truss displayed an incorrect return value for lseek().
250562
truss displayed invalid names and opcodes for msgsnd/rcv.
250582
Some shared objects were not unmapped after a dlclose() operation succeeded.
250587
When a multi-threaded application invoked the FIONBIO or FIOASYNC ioctl on a BSD socket, problems could occur on the socket and eventually panic the system.
250588
The qfork(2SEQ) man page was not formatted correctly.
250605
An hdsinfo(1) man page was needed.
250630
The SCI bootloader could lose messages, causing the system boot to fail.
250636
When a writev() system call was issued on a fifo pipe, the system hung and eventually panicked.
250637
usleep() did not handle the granularity of timer values properly.
250642
The proc_ctl(2SEQ) man page did not document the commands PROC_RELINQUISH and PROC_OPENT.
250655
Page faults occurring outside of the normal 3-GB user virtual space did not always generate information for the SIGSEGV signal.
250664
config no longer needed asm long long support.
250668
The mpt driver did not set a value correctly.
250671
The find(1) man page contained a typo.
250688
Problems could occur when processes with multiple LWPs were migrated.
250694
A value in sysinit() was not initialized correctly.
250724
The system could panic when a null LWP was passed to an internal routine.
250740
A problem with application regions caused the system to panic.
250751
A threads component was needed to report threads metrics.
250930
An internal kernel variable used for diagnostics could not be accessed by the bp program.
251032
When configuring the kernel with ptx/ADMIN, the "Config files with adjustable parameters" screen contained an invalid entry.
251033
The system panicked with the message p_sema: called when sleeping illegal.
251039
A problem with an internal threads routine caused the system to panic.
251070
dlopen() did not increment the reference count of a file if it was opened again.
251331
The virtwinv_synctlb(2SEQ) man page did not specify the correct return value.
251341
A problem in the console module could cause a hang during a system shutdown or panic.
251516
cpio failed when a scratch install was performed with an EFS filesystem.
251564
A race condition in an internal routine caused the system to panic.
251609
The ptx/ADMIN "per-quad dumplist" option did not update /etc/dumplist correctly.

ptx/C and Programming Tools

237525
The ptx/C preprocessor handled concatenation differently than other compilers.
241107
debug needed to display a message when it encountered a threaded process.
245202
When the -Bexport option was used, ld crashed while trying to link a .so file.
247439
elf_demangle()did not properly demangle ptx/C++ symbols.
248245
debug could not set a watchpoint using an address constant larger than 0x7fffffff.
248373
Syntax errors occurred when a program was compiled with the -K PIC flag.
248617
There was a memory leak in the elf_demangle() routine.
248841
acomp failed with the following message: internal compiler error: confused cg_inflush().
248887
ngen could not determine the type of a variable that was used but not set.
248915
The ld -r option could cause memory corruption.
248970
When the -KPIC option was used, the compiler did not always recognize the asm macro.
249231
The cc(1) man page did not document the -W1,-saferet option.
249679
The debug map command did not interpret PROT_NONE permissions correctly.
250640
ld made incorrect .rel section entries for undefined weak symbols.

edb Debugger

240978 [3202]
edb did not demangle the names of functions if it could not determine the language used for the functions.
247479 [3913]
edb reported the argument list incorrectly for the struct return value.
248385 [4090]
edb did not debug a process after an exec.
249156 [4211]
edb issued the confusing message warning: HandleDyn: cannot read _r_debug.
250648 [4416]
edb lost a breakpoint in a shared object.
250650 [4418]
edb could not handle long pathnames on the command line.
250654 [4419]
When a program running in the foreground was interrupted, edb stopped in _rt_boot.
250660 [4422]
The edb stack command did not display system call arguments correctly.
250678 [4430]
edb sometimes lost a stack frame when it hit a breakpoint that was set at a system call.
250714 [4442]
The default value for the returnrepeats option needed to be changed to zero.

Problems Fixed in the V4.5.0 Release


Base Operating System

13969
make did not list the dependencies when a makefile contained a dependency cycle.
18321
The TCP port for remotelp was hardcoded as 515.
18974
The error message for allocb() did not provide enough information.
19343
The permissions for /dev/swap were 440 instead of 660.
19393
The bdflush(1M) man page did not specify the default values assigned to the arguments autoup and flushrate.
19968
init did not take the appropriate action when it found an incorrect entry in /etc/inittab.
20135
The sh shell did not remove work files when HERE documents were used.
23161
An I/O error was generated when data was piped into the strings command.
23162
The strings command did not print all of the strings that it found.
23163
ptx/ADMIN did not understand shell variables specified in crontab files.
23354
mailx set file modes incorrectly.
23364
awk sometimes incorrectly handled strings containing more than 24 characters.
23368
The compress(1) man page did not describe the behavior of the command when used in a pipeline.
43777
When lpsched or remotelp were started in a filesystem other than root, they prevented other filesystems from being unmounted.
47978
The default date/time format string was incorrect for the United Kingdom.
48469
The e command in the vi editor ignored words consisting of a single character.
201044
The catgets(3C) and catgetmsg(3C) man pages did not specify the appropriate action when catd was -1.
202335
catgets() dumped core when a message catalog had a value of -1 and the program was compiled with the -z option.
202741
uucheck did not report problems with file permissions on UUCP files.
209967
ct and uugetty could not be used together.
210626
The gcore(1) man page did not describe restrictions for using the command.
210647
The newfs -c option did not work correctly.
212208
The df(1M) man page did not describe the -f option.
213544
fsck -M could fail if there was insufficient swap space.
213891
A startup script was needed to verify that the system was set up properly to save crash dumps.
215260
If the PARALLEL environment variable was set to 1 and ptx/ADMIN was used to compile the kernel, the compile could hang.
215367
The crash f1 command could not identify the type (UFS, EFS/CFS, NFS) of a file lock.
216827
An existing mandatory lock became invalid after a file was truncated with truncate() or ftruncate().
217536
ksh did not process the syntax ((...)) correctly.
217722
The POSIX macros in sys/stat.h did not work correctly.
217900
ptx/ADMIN created custom VTOCs with smaller partitions than the user requested.
218630
uudecode did not decode everything in a file.
219020
fsck did not correctly handle a corrupted UFS superblock.
219341
A program using the m_fork() routine could hang when it received a signal.
220025
The truss man page did not specify that the command displays incorrect values for system calls called with syscall().
220945
expr did not support 64-bit arithmetic.
221530
The privctl(1M) man page needed clarification regarding its use by non-root processes.
223056
The vi option ignorecase did not work correctly.
223351
The sh(1) man page did not describe how the shell handled traps.
223547
When the mountall command was used, fsck attempted to validate filesystems whose type was set to "ignore."
223754
The dlopen(3X) man page did not describe the -Bexport linker option.
223751
When a new kernel was built, the message FILE ($unix_tbi) NOT FOUND could be incorrectly displayed when the system was booted.
223755
MAKEDEV generated unnecessary errors.
223765
The tar command did not work for /.
224042
When /etc/dump was killed, it did not remove the semaphores it had created.
224034
ps did not have an option to generate output in a machine-parsable format.
224037
The cd(1) man page did not specify that the syntax cd old new applied only to the ksh shell.
224042
When /etc/dump was killed, its semaphore set was not removed.
224146
Output from cron did not specify the job that generated the output.
224289
The link(1M) man page did not warn that ln should be used instead of link.
224842
The open(2) man page did not describe several DYNIX/ptx-specific flags.
225252
make -P did not set the PARALLEL environment variable.
225382
The name of the FDIV_BUG tunable parameter was changed to eliminate warning messages during kernel compilations.
225455
An error message appeared when the ptx/ADMIN "Alt Disk Compare" menu option was invoked.
225554
The MAKDEV -P option did not work correctly.
225686
When a window was resized while using more, the echo flag was turned off.
225800
lpadmin needed an option to set the retry time for a print job that was rejected by lpsched.
225847
The cfg_sys() system call had mismatched arguments with respect to the kernel and the library entry point.
225883
Certain programs did not run correctly across NFS.
225909
The executable /usr/bin/rmchg was incorrectly supplied on the distribution media.
225911
more did not display bold text correctly.
226249
The MAKEDEV(1M) man page did not describe all of the options.
226310
cpio did not copy hard links with the -p option if the -c option was also specified.
226370
The creat(2), open(2), fopen(3S), truncate(2), and intro(2) man pages did not document the EBUSY return value.
226538
/etc/umountall did not recognize the -o filesystem-specific options.
226636
crash printed arrays of structures incorrectly.
226815
A DYNIX/ptx-specific limit was needed for the maximum number of concurrent asynchronous I/Os per process.
227025
When the root filesystem was under ptx/SVM control, an error message appeared during system boot.
227296
getpwnam() behaved differently with the dynamic library.
227402
An unsigned long long type definition in sys/types.h caused a C++ warning.
227451
On NUMA-Q systems, VCS was not always notified when the system changed state from single-user mode to multiuser mode.
227632
An internal RPC routine contained a memory leak.
227642
The default value for the SYMLINK_MAX kernel parameter was too low. (The new default value is 64.)
227756
The help file for the ptx/ADMIN "Software Management" menu was out of date.
227854
rqstat reported an incorrect value for the number of processes in a run queue.
227877
The more(1) man page incorrectly stated that when more was invoked on multiple files, a header would be printed before each file.
227901
The bp(1M) man page did not describe the syntax correctly.
227974
ps needed an option to display additional run queue information.
228039
adb was removed from the public software product.
228195
/bin/login set the stty values for rows and cols to zero.
228357
The output from kill -l no longer included numeric values. (Use the new -v option instead.)
228388
The at command did not set variables if /bin/csh was the default shell.
228461
Examples in system files used zd disks instead of sd disks.
228831
If a crontab file contained two entries with the same command, the second entry could not be changed with ptx/ADMIN.
229072
The infodev(1M) man page did not specify that for sequential access devices, the media must be mounted in the drive.
229099
New snprintf and vsnprintf routines were added. See the printf(3S) and vprintf(3S) man pages.
229214
newfs and mkfs incorrectly rounded a large value supplied for the -i option and failed to create the filesystem.
229406
ln -f did not work if files were already linked.
229408
/usr/include/ftw.h contained a syntax error.
229545
The fpgetround(3C) man page was out-of-date regarding ELF binaries.
229560
The parameters for the rpcb_getaddr() function were out of order in the rpcbind(3N) man page.
229604
devbuild displayed a redundant entry on Symmetry systems.
229710
truss did not produce output for SDAEMON processes other than init.
230200
index() was defined incorrectly in libgen.h.
230217
The select(3C) man page contained incorrect information regarding the rounding of timeout values.
230347
The ptx/ADMIN ktlogmaint utility did not work correctly.
230455
The mount and newfs commands did not check the partition type.
230468
A scsitape routine could sleep for a long time before returning EBUSY.
230635
The default .profile file had redundant definitions for the ERASE, KILL, and INTR terminal settings.
230652
libdl.a was not exported.
230696
Control files for the naming database should have been in /var/run instead of /dev.
230689
diskid truncated device names containing a non-alphanumeric character instead of terminating.
230696
The control files for the naming database were located in /dev instead of /var/run.
230855
The ptx/ADMIN bootflags.data file did not contain an example for NUMA-Q systems.
231195
The description of the -n option in the df(1M) man page was incorrect.
231384
The PIOCSIGNAL and TIOCREMOTE ioctls were missing from the ptem driver.
231410
When a large number of filesystems were mounted, the ptx/ADMIN "Set Boot Flags and Strings" form took too long to appear.
231448
When prompting the user for a terminal type, ptx/ADMIN listed vu320 last.
231911
ptx/ADMIN could not be used to add SVM volumes to the vfstab file.
231746
The dumpconf(1M) man page needed examples for the -b and -r options.
231912
Error messages from the ptx/ADMIN form "Add filesystem entry in /etc/vfstab" were removed too quickly.
231920
The ptx/ADMIN "Configure a Kernel" option contained outdated examples of ptx/SVM disk names.
231943
more did not determine EOF correctly.
231980
The savecore utility needed to save dumps specified by both the temporary and permanent dump paths.
232107
When there was a discrepency between the system boot file, the device name configuration, and/or the bootflags, the system did not report the incorrect physical path or swap device.
232110
Mount structures were not allocated dynamically.
232112
proc_ctl() was not defined in a header file.
232158
Man pages were needed for the bfset and bfget commands.
232343
The more command did not specify that q should be used to exit the display.
232435
The siginfo(5) man page needed clarifications.
232767
The scsidisk and scsitape space files contained unreferenced variables.
233019
The system did not verify that the primary swap device was not shareable.
233020
The param_space.c file contained an incorrect comment that parameters could be changed using "options."
233046
dump did not record write() errors effectively.
233182
The output from ls -l ran together when the owner or group name contained more than eight characters.
233185
The compiler option -D__ NO_LONG_LONG did not work properly.
233208
devctl -t failed if all devices of one type were deconfigured.
233503
The definition of the timeval structure in sys/types.h did not match the definition in sys/time.h.
233741
The dumpconf(1M) man page did not describe the output when a child or parent port did not exist for a device.
233838
The SCSI driver reported I/O errors when I/O was present and a second node joined the cluster.
233864
The read(2) and write(2) man pages specified the wrong return type for functions.
233950
The crontab(1) man page assumed that the interrupt key was set to DEL.
234091
mkvtoc allowed unprintable characters in the string representing the disk type.
234126
ksh ran a while loop only once if the EDITOR environment variable was not exported.
234183
The ptx/ADMIN "Filesystems Management" menu did not list SVM volumes when the user pressed SELECT.
234230
csplit limited the line length to 256 characters.
234309
The vi(1) man page incorrectly stated that the use of < and > was not supported.
234393
The stty(1) man page did not describe the options and operands correctly.
234401
The -lmalloc version of malloc() did not work properly with select().
234447
When given a value greater than or equal to INT_MAX, the sleep command would return immediately.
234507
The ptem(7) man page did not describe the TIOCSIGNAL and TIOCREMOTE ioctls.
234515
A component of the interface to the timeout event scheduler system used an incorrect data type.
234769
A vectored version of virtwin() was needed for database writers.
234841
When top2 was invoked with the -t option, it printed an incorrect minimum value.
234954
Some of the prototypes in the qexec(2SEQ) man page were incorrect.
234986
The man pages for the strtol*() routines did not include stdlib.h.
235205
The cfg_info man page needed to be moved to section 3SEQ.
235206
truss output for commands accessing cfg_sys() was not in decimal.
235259
The kernel did not generate a warning message when record locks could not be granted.
235319
mkdir did not support the s, l, and t permission bits.
235366
The cfg_sys(2SEQ) man page referred to undefined symbols.
235380
The UFS version of fsck allowed the mounted root filesystem to be modified. (A new option, -o modifyroot, must now be specified to modify the root filesystem.)
235561
The operating system did not issue a warning when there was not a V-FW partition on the boot disk.
235647
vi did not perform reverse searches correctly.
235652
make dumped core when a huge macro was defined on the command line.
235759
The join command ignored the last field separator.
235828
The ualarm(2) man page specified usleep() instead of ualarm() in the synopsis.
236013
A warning was not generated when the length specified in the primary swap label did not match the device size.
236014
The SIGINFO macros in siginfo.h should have been included only by the kernel.
236037
cpio and pax did not preserve the UID/GID for symbolic links.
236144
/etc/vdc was started on Symmetry systems.
236164
A man page was needed for the mountfsys and umountfsys commands.
236163
A man page was needed for the bupsched command.
236178
The usage message for prtvtoc did not include the -T option.
236187
Special characters in a tags file were not preceded by a backslash, causing vi to treat them as a regular expression.
236405
fsync() failed with EINV for pipes.
236445
The bcheckrc(1M) man page specified the wrong paths for bcheckrc and bcheckrcsau.
236541
The sort(1) man page did not show the correct syntax for the -T option.
236542
When mailx was invoked with the -r and -s options, the delivered mail did not contain a Subject field.
236599
egrep returned incorrect data on long lines.
236661
sed did not recognize the regular expressions \< and \>.
236706
ksh did not detect a loop end that was entered from the keyboard.
236765
A process running an rc0 script could lose script input to children.
236838
t_rcv() could block forever in the T_UNBND state.
236965
Timeout-event load balancing did not work properly across processors.
237008
sadc wrote titles only to a new data file.
237164
The mailx -r option was not documented properly in the man page or the usage message.
237214
The attach_proc(1M) and attach_proc(2SEQ) man pages did not specify that the run queue for a process must include processors on at least one of the quads where the specified resource is located.
237264
The klogd(1M) man page specified the wrong location for the startup script.
237320
The virtual memory system did not track the allocation of hardlocked memory segments.
237338
A high rate of synchronous raw disk I/O caused buffer contention.
237354
The select(3C) man page referenced the wrong header file.
237377
chown did not fail properly when the user's UID was out of range.
237554
A problem with long filenames on CDFS filesystems caused an infinite loop.
237609
A problem with memory allocation routines could possibly cause memory corruption.
237628
A race between exit() and an internal routine could cause the system to panic.
237661
remotelp used the obsolete getpeerinaddr routine.
237782
The getty(1M) man page did not specify the naming conventions for TTY lines.
237857
sort dumped core when used with a large number of files.
237865
vi could be started in the background.
237890
login set the default PATH to begin with the current directory.
237898
make did not expand a macro correctly if its name began with an underscore.
237927
The fabric and scsibus drivers did not have per-quad active I/O counters.
237943
By default, tar attempted to remove the file /tmp/tarXXXXXX on exit.
238038
The library function t_alloc returned the wrong type.
238040
The tistat command did not allow an alternate kernel name to be used to access symbols.
238041
The tistat(1M) man page did not describe the -u option.
238042
tistat did not allow the use of an alternate kernel name.
238085
Global process state counters were converted to multiprocessor counters.
238086
Global good/bad IO counters needed to be removed.
238122
crash needed a utility to evaluate multiprocessor counters in the kernel.
238251
The devt_to_name(3SEQ) man page did not specify the header where the prototype of the function is defined.
238301
Output from ipcs -ma was corrupted when the command could not access a shared memory segment.
238428
When fclose() failed, it returned EOF and did not set errno.
238430
If a user logged out of a system that had run out of file or record locks, the user's utmp entry was not deleted.
238431
An interface was needed to audit file security information.
238485
The su command did not determine whether the password for the specified user had expired.
238508
The date(1) man page did not describe the %W and %U options correctly.
238574
Buffer cache deadlocks caused the system to hang.
238703
ksh did not interpret a << operator correctly when it was enclosed in double quotation marks.
238720
mail had an off-by-one bug.
238734
Stream queues were not allocated dynamically.
238735
Stream headers were not allocated dynamically.
238737
CDFS mount structures were not allocated dynamically.
238806
The timezone(1) man page was ambiguous about Julian dates.
238882
file did not specify whether the symbol table had been stripped from an executable file.
238885
Session structures were not allocated dynamically.
238909
The message Large 64-bit PTEs are configured with all physical memory below 4GB appeared at system boot.
238911
The /etc/rc2.d/S30autoconfig script did not set up the ptycompat devices correctly.
238941
The symbolic_stack option in /etc/system/boot was not enabled by default on NUMA-Q systems.
239011
fsck sometimes incorrectly resolved extraneous hard link names.
239123
The DIO(2SEQ) man page did not specify that EFS and CFS filesystems support ASYNC DIO.
239149
file did not check the error status when a read failure occurred for the given file.
239174
od printed an extra space at the end of a line.
239190
mailx incorrectly saved mail in $HOME/mbox.
239377
The unistd.h header file did not provide the prototype for sethostname().
239859
The monitor(1M) man page did not include the amount of free memory per quad in the list of activity monitors.
240163
Fifo structures were not allocated dynamically.
240176
An rc script was needed to modify kernel parameters at boot time.
240203
The message APIC err: 0x40 was displayed during a normal shutdown.
240224
The perror(3C) man page needed to document that the size of the sys_errlist[] array was changed, breaking binary compatibility. The man page recommends that strerror be used instead.
240467
The file descriptor tables were not allocated dynamically.
240543
The default baud rate for ptem was too low. (It has been increased to 38400.)
240564
ptem modules were not allocated dynamically.
240570
The mt device issued an ambiguous message when it could not execute the clearerr command.
240604
auconfig did not have an error code to report that the user did not have superuser privileges.
240699
fsck -M did not mount filesystems in parallel.
240704
The cdfs unmount code contained an unnecessary check to determine whether the device was used for swap.
240766
UFS disk quota structures were allocated statically.
240772
The timezone(4) man page contained incorrect information about the alternate time zone.
240782
A problem with a kernel memory routine caused the system to panic.
240847
The dmesg buffer was not big enough to capture a stack trace on a NUMA-Q system.
240850
ps did not display data if other options followed the -t termlist option.
240860
The reex.hg header file did not include the REG-WORD flag. See the regcomp(3X) and re_format(5) man pages for information about its use.
241004
When print requests were sent to networked printers that did not support remotelp, the lp -n option did not work correctly.
241052
ieeefp.h did not contain an isnand() prototype.
241156
Certain kernel-specific flags in sys/file.h needed to be visible to _KMEMUSER.
241222
/etc/cleanup could remove all files in the root filesystem.
241391
The script /etc/rc2.d/scandump could not locate disks having names other than qdxx or sdxx.
241399
The fcntl(2) man page did not describe the F_SETOWN and F_GETOWN flags.
241567
file could not classify JavaTM class files.
241960
The patent and copyright information in /etc/motd was out of date.
241967
In ipcs output, the memory address began with Ox instead of 0x.
242112
A problem in the libc implementation of the getcontext system call caused the esp register to be restored incorrectly after the setcontext call.
242127
A race existed between exit() and an internal routine.
242139
The df -P command displayed a negative value for filesystem usage.
242725
Certain error messages could include an incorrect code path.
242800
The unix(8) man page did not describe the -W option.
242807
The rdcp(1) man page incorrectly stated the default value for the MAXAIO kernel parameter.
242885
An I/O problem caused the system to panic.
242903
The tr command dumped core when the [:cntrl:] option was used.
243109
The system panicked with the error Panicstr: ialloc: dup alloc.
243166
The poll/pollresetall calls needed to be optimized for faster performance.
243208
An internal routine contained a potential speculative execution problem.
243265
A bad MDC QMI message caused an Infinite MMU fault.
243304
The touch(1) man page did not completely describe the -t option.
243310
useradd incorrectly called a shell command to access the password file.
243336
The wc command did not detect or report read errors.
243340
The DirectIO(2SEQ) man page incorrectly stated that only UFS was supported.
243451
The syntax shown in the dump(8) man page was incomplete for NUMA-Q systems.
243501
Certain regular expressions caused sed to hang.
243512
The stand-alone dump command did not issue its own state-change messages.
243649
The /etc/magic file used by the file command was out of date.
243799
The rcs -Aoldfile command did not work correctly.
243810
shmget() held shm_sema while allocating backing store for a segment, preventing other shmget or shmat families of calls from occurring.
243825
Permissions on crash dump files needed to be more secure.
243828
The kernel could not limit snode allocations.
243842
An overflow condition in specfs could cause silent data corruption.
243864
The system could panic when a driver tried to set or change the quad affinity for a stream.
243947
A wtmp_avail file was needed to record uptime information for SequentLINK.
243999
The ndbdump(1M) man page did not state that the command can be used only by root.
244000
ndbdump displayed a confusing error message when invoked by a user other than root.
244001
The ndb_ctl(2SEQ) man page did not state that nbd_ctl() can be called only by processes with superuser privileges.
244041
Requests for process-to-process attachment sometimes failed silently.
244054
The vmtune command did not handle large values as arguments.
244082
A problem with the qlc driver caused the system to panic.
244106
setrlimit() allowed a brk segment larger than 2 GB - 1 to be set.
244153
The kernel did not allocate enough structures for FC components.
244163
ksh did not handle recursive functions correctly.
244167
When a sync_op operation failed, it did not return the number of operations that completed successfully before the failure.
244196
The strftime(3C) man page did not specify that strftime can modify its static buffer.
244253
The dis386(3SEQ) man page did not describe the third argument of the routine.
244262
Header files with long long did not allow C++ long long support.
244294
Header file modifications and library changes were needed for wide character support.
244310
When in prolonged use, remotelp slowed down and consumed memory.
244338
The dis command did not always display the rep prefix correctly.
244362
dircmp could not handle pathnames containing spaces.
244438
The pdcd daemon needed to be added to /etc/rcp.
244458
The times(2) man page did not specify that the return value could overflow the possible range of type clock_t.
244484
When many new disks were added to the system, some device nodes were not created during system boot.
244534
A problem with a pending signal caused klogd to dump core.
244582
The system hung when downloading firmware with ffutil.
244621
An internal Fibre Channel routine did not always free memory correctly.
244682
The ptx/ADMIN RPC Management menu displayed in English when LANG was set to another locale.
244724
The quad_loc(2SEQ) man page did not specify the return type for the function.
244726
The quadset(2SEQ) man page referenced execq instead of qexec.
244747
devctl -d could cause systems with certain FC configurations to panic.
244803
getopt dumped core when the length of the argument list was greater than the maximum allowed bytes in the exec argument list. The command now prints an error message when this situation occurs.
244889
Multiple mmaps of large files could cause the system to panic.
245028
crash skipped a frame in MMU fault stacks.
245037
The libc version of valloc() caused a segmentation fault.
245038
A system call was needed to set target values for the kmem structure.
245071
A race in an internal routine caused the system to panic.
245097
System calls made by layered products could not be traced.
245104
sadc read /dev/kmem to get overflow statistics instead of using getkerndata().
245124
uptime read /dev/kmem instead of using getkerndata().
245135
ipcrm could not remove keys that had the high bit set.
245145
The mpt device could retry a bad route repeatedly.
245160
The snode command in the crash utility did not work properly.
245207
Multiple processes could access the pass-through control device, causing the system to panic.
245208
A problem with a kernel virtual-memory allocation routine caused the system to panic.
245256
/bin/make failed when the size of the macro specified in the input line exceeded BUFSIZ.
245289
The ff driver could lose its "target mode" buffers.
245344
A UFS routine had an overflow problem.
245455
Callers of the disksort() routine could manipulate the queue buffer directly and cause the system to panic.
245493
A change to sed broke compatibility with the earlier version of the utility.
245758
The system could panic when truss was tracing page faults.
245761
The scsibus layer did not use all available initiators to avoid errors.
245804
A function in the timod driver did not free previously timed-out ioctl message blocks.
245823
The system panicked when VCS was closed and then reopened.
245942
dis386() disassembled rdpmc as rpdmc.
245960
dis386() incorrectly disassembled 0x0fff as ud2.
246034
A problem in a Fibre Channel routine caused the system to panic.
246101
The system could panic when truss was tracing a page fault.
246375
A libm function did not round in accordance with IEEE 754.
246379
The code that parses devinfo files incorrectly handled tokens that did not have an associated value.
246442
debug could not read core files generated by the Java virtual machine.
246572
When an FCP port to a Hitachi DF400 device was lost, the remaining port could not be used.
246643
The system could panic when the FC bridge was probed after a boot.
246867
sed did not handle substitution at the end of a line correctly.
247302
A race problem with the filesystem buffer cache could cause data corruption.
247338
A problem with an internal mpt routine caused the system to panic.
247557
mmap() needed the MAP_NORESERVE flag to specify that a given private anonymous mmap use a dynamic swap allocation policy, even if the current system default is to prellocate all swap space.
247612
On NUMA-Q systems with a single quad, the mpt driver did not perform an age calculation correctly.
247684
The ff driver accessed a port data structure after it had been freed.
248049
nl_langinfo(CODESET) returned an empty string for locales other than POSIX/C.
248495
A problem in the virtual memory subsystem could cause data corruption.
248593
The system could panic if an extraordinary memory-depletion condition occurred.
248596
The system panicked with Context does not hold AS lock in WRITE mode.
248683
The scsibus driver could panic if Pbay commands failed.

ptx/C and Programming Tools

211992
Additional optimizations were needed when code was compiled with -O or -Wc,-Osz.
231837
lint did not issue a warning for a function call that was made through a pointer and that ignored the return value.
232079
lint did not display a message giving the location of the first declaration of an identifier that was redeclared or redefined.
233119
lint did not warn for all unsigned comparisons with zero.
233466
The compiler did not dereference (volatile char *) correctly.
236575
ld needed an option to list directory pathnames used to specify library search directories to the run-time linker.
237255
lint did not issue a warning when int and long were mixed with the -= operator.
237256
lint generated unnecessary warnings when an xor operation was used.
237355
lint did not report all instances where the assignment operator = was found but == was expected.
237406
A floating-point comparison with NaN did not comply with IEEE 754.
239988
When looking up symbol names, dlopen() did not scan the local symbol table first.
240368
ld -r attempted to resolve undefined weak references.
240651
dump -D did not recognize all DWARF debug information.
241664
cprs did not handle nested subroutine types correctly.
241783
ld generated a SIGSEGV when opening a shared object.
242330
cprs did not work properly on ELF shared object files.
243104
debug printed an inconsistent state error for C++ data types.
243186
mcs failed if the .strtab or .shstrtab sections of a file had been deleted.
243210
debug printed void pointers as integers in stack traces.
243838
The cc(1) man page did not document the __STRICT_ANSI__ predefined macro.
243839
The cc(1) man page documented the obsolete symbol w1167.
244058
The ofl_dump utility was not documented. (See the new ofl_dump(1) man page.)
244359
An assertion failure occurred when a computation was used before it was defined.
244552
The lint warning for %0p was changed from malformed format string to portability warning: "%0p" behavior is undefined by ANSI C.
244657
The m4 option -Bint accepted a space between -B and int.
244860
The compiler needed to define __STDC__ to be 1 rather than 0 for the -Xa mode of compilation.
245073
Instructions inserted between branches caused an assertion failure.
245302
An optimization incorrectly deleted a compare instruction.
245527
The compiler did not issue a warning when the keyword volatile appeared in a cast.
245959
The assembler assembled ud2 as 0x0fff instead of 0x0f0b.
246160
In certain cases, integer to float conversions were converted to double instead of float.
246315
The compiler did not compute -0.0 correctly at runtime.
246848
The description of the -Wc,+dir option in the cc(1) man page did not specify that the driver uses only one dir/cc_options file.
247485
A structure argument was temporarily pushed on the stack before it was initialized.
248234
debug caused the process being debugged to inherit debug's signal mask.

edb Debugger

240276 [3125]
edb could not display an istream argument and reported arithmetic error.
240832 [3185]
edb needed to support the C and C++ long long data type.
241108 [3268]
edb needed support for debugging threads.
241855 [3279]
edb experienced an internal error when attempting to deference an incomplete type.
242065 [3293]
An edb watchpoint was sometimes reported as a SIGTRAP signal.
242553 [3309]
edb disassembled xor %ch, %ch as xor %ch, %ebp.
243131 [3373]
edb sometimes died when trying to debug a core file for which there was a C++ executable and a C shared object that was compiled for debugging.
243198 [3389]
edb failed to print variables and function pointers.
243276 [3397]
edb did not support setting a breakpoint in a global function from a shared object that was accessed via dlopen().
243619 [3448]
edb needed a wait command for automated testing.
243620 [3449]
edb commands for thread support were inconsistent.
243624 [3451]
edb needed an option for a blank line to be treated as a comment.
244094 [3493]
edb needed to support disassembly for new processors.
244559 [3539]
edb needed an option to suppress the automatic update of the current job.
245066 [3623]
edb disassembled the instruction 0xF2 0xAE (rep scasb) incorrectly.
245388 [3673]
When forked processes were debugged from commands redirected from a file or read from a command script via the read command, breakpoints were reported as SIGTRAPs.