[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hpux-devtools
Subject:    HPUX-DEVTOOLS: HP WDB 3.3 available
From:       "Jansi" <ajansir () india ! hp ! com>
Date:       2003-10-28 6:37:17
[Download RAW message or body]

Hello All

    The Wildebeest Debugger Team is happy to announce the latest release, HP
WDB and WDB-GUI 3.3 for 11.0 and 11.11 HP-UX (PA) systems. It is available
for free download at http://www.hp.com/go/wdb.

The new enhancements to this version are:

==============================================================
New features in HP WDB and WDB-GUI 3.3

HP WDB 3.3 includes the following new functionality and defect fixes:

**Implementation of ask mode for set follow-fork-mode:
	This command prompts user to select between parent and child as the
debugger response to a program call of fork/vfork. Based on the user
selection, the parent
or the child process is debugged.

For example:
(gdb) set follow-fork-mode ask
(gdb) show follow-fork-mode
Debugger response to a program call of fork or vfork is "ask".

(gdb) run
Starting program: sample
[New process 4941]
warning: reading `r3' register: No data
Select follow-fork-mode :
[0] parent
[1] child
>

Version 3.3 of the WDB GUI includes the following new feature:

** Memory Log:
	This release of WDB GUI supports a new feature, Memory Log. The Memory
Usage view reports data that the debugger collects on your program's memory
leaks and heap use. The Memory Log feature enables you to save these reports
to a file on the disk.

=================================================================

Summary of Changes in HP WDB and WDB-GUI 3.2

HP WDB 3.2 includes the following new functionality:

*Support for a new command, dumpcore
	HP WDB 3.2 provides a new command, dumpcore, to generate a core image file
for a process running under the debugger in the middle of execution. The
dumpcore command does not require any argument. It saves the core image for
the current process being debugged in the file named core.<pid>, where <pid>
is the process ID number. To generate and analyze the core file with HP WDB,
refer to the following sample code:

To dump the core for a live process, you must pass the following commands:
(gdb) run
Starting program: sample
Breakpoint 3, main () at sample.c:1010
b = foo(a) ;
(gdb) dumpcore
Dumping core to the core file core.24091
(gdb)

When starting from HP WDB command line:
(gdb) set live_core 1
(gdb) core-file core.<pid>
(gdb) file sample
Reading symbols from sample...done.
(gdb) set live-core 1(gdb) core core.24091
Core was generated by 'sample'.
#0  main () at sample.c:10
10     	b = foo(a) ;
(gdb) backtrace
#0  main () at sample.c:10
(gdb)

When starting from shell prompt:
% gdb --lcore a.out core.<pid>
% gdb --lcore sample core.24091
HP gdb 3.2 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 3.2 (based on GDB) is covered by the GNU General
Public License.
Type "show copying" to see the conditions to change it and/or distribute
copies. Type "show
warranty" for warranty/support
....
Core was generated by 'sample'.
#0  main () at sample.c:10
(gdb)

*Support for enabling and disabling threads
	While debugging a multi-threaded application, if you suspect that a
specific thread is causing a problem, suspend other threads in the debugger
and debug the doubtful thread.

*Support for the steplast command for both C and C++
	HP WDB 3.2 includes the steplast command, which helps to step into a
function, and not into the calls for evaluating the arguments. In C++, the
steplast command is helpful while debugging heavy templated functions,
because it directly steps into the call, thus skipping the constructor
calls, if any. This behavior is unlike the step command that steps into the
constructor itself.

*Additional support for command line calls in a stripped executable
	HP WDB 3.2 enables you to perform command line calls in a stripped
executable for 32-bit applications, without the help of dynamic
linker(end.o) and for 64-bit applications, with the help of end.o.


Version 3.2 of the WDB GUI includes the following new features:

*Enable/Disable Thread:
	While debugging a multi-threaded application, this feature allows or
prevents a thread to run when you execute the step or continue command. A
disabled thread is indicated by a 'D' symbol before the thread id in Threads
View.

*Support for the "steplast" command for both C and C++:
	HP WDB GUI 3.2 includes the steplast command, which helps to step into a
function, and not into the calls for evaluating the arguments. This feature
is now supported for both C and C++.

=================================================================

For more information on features/fixes of WDB and WDB-GUI, read the
releasenotes on the download page or follow the links:
   www.hp.com/go/wdb
       --->documentation
           --->"HP WDB 3.3 Release Notes"
		 (or)
           --->"HP WDB GUI 3.3 Release Notes" respectively.

Hope you all enjoy using the new debugger WDB and WDB-GUI, Version 3.3. We
would be happy to hear your comments and feedback.
See our web page for contact information.
 _________________________________________________________________
 To leave this mailing list, send mail to majordomo@cxx.cup.hp.com
    with the message UNSUBSCRIBE hpux-devtools
 _________________________________________________________________
[prev in list] [next in list] [prev in thread] [next in thread]