The disable command produces misleading
information for multi-threaded programs.
The pxdb fails with an out of memory
error message while reading files of size 2 GB.
WDB incorrectly reports heap object registered with
different size when an application is compiled with +check=bounds:pointer to perform out of bounds check.
WDB incorrectly reports value of thread-local variable.
The next command fails to step
into a forked child process.
WDB does not recognize pack core filenames with extensions
other than .tar.Z. If the application is compiled
with +check=memory, it crashes while WDB attempts
to print the memory information.
Batch RTC fails even when the output_dir command is set and the current working directory does not have write
permission.
WDB is unable to perform Java debugging.
GDB crashes while printing the type and value of the
structure member of array type with array of size MAX_INT_32.
GDB crashes while reading the elf large section details
of the application that contains large number of sections.
GDB crashes while printing the type of the member
function of the class whose function name is similar to that of function
name in standard libraries.
Occassional gdb crash with batch mode thread check
when application aborts. On running batch mode thread check on applications
that crash or if Ctrl-C is executed while the application
is running, gdb crashes.
Occassional hang with batch mode thread check, when
the application has an incorrect usage of pthread_cond_wait()() call.
