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

List:       hpux-devtools
Subject:    HPUX-DEVTOOLS: FW: CXX-DEV: Request for Requirements for the WDB debugger
From:       "Banibrata Dutta" <dutta () india ! hp ! com>
Date:       2005-09-16 18:48:33
Message-ID: 200509161902.AAA06038 () harvest ! india ! hp ! com
[Download RAW message or body]

Since I saw no comment on this one, re-forwarding it. But then, may be ideas
were not that great to comment on!! :)

-bd 

-----Original Message-----
From: Banibrata Dutta [mailto:dutta@india.hp.com] 
Sent: Thursday, September 15, 2005 10:36 AM
To: wdb-help@cup.hp.com
Subject: FW: CXX-DEV: Request for Requirements for the WDB debugger

Hello WDB Team:

I start by congratulating you for an excellent release (5.2). I've gone thru
(almost entirely) the 5.2 part of the RN, and features are impressive. I've
used only 5.1, and that to works quite well.

One feature which I had quite recently requested from a local
wdb-team-member (thru a personal interaction), may be worthwhile
consideration.

Description: Presently for getting heap-usage-profile or to do memory-leak
detection in Batch mode (BATCH_RTC), the target process must call
exit()/_exit(), as that's where the RTC hook computes & dumps leaks/usage.
For certain types of processes, this is not possible. Either it's not
possible to modify code to call exit(), also, this doesn't allow for
incremental leak-detection to be done. So here's the enhancement I
suggest...

In case it is possible to modify code of target process, then...

Permit the use of a special function, say -- rtc_dumpleaks() or something,
which when invoked by the running process itself, dumps a report of the
leaks, and the process carries on doing what it was doing. So each time it
dumps the report in a unique file (named to include PID & date/time of
dump). The the program can be made to invoke this function under some kind
of user-control, e.g. when i send it SIGUSR1 (& the program is coded to
handle it this way).

In case it is not possible to modify code of target process, then...

Maybe add a special library which is loaded thu LD_PRELOAD, whose job could
be to start an independent thread (immediately after main() is invoked), and
this can also expose a telnet-server based CLI (command line iface.), to do
allow interactively trigger heap-usage/leak-detection algo to run, and dump
a report on terminal, or a file. Since this is an independent thread, which
is not coded into the original program, program modification is unnecessary,
but being a thread it should have access to entire process address-space
(except probably thread-specific-storage).

thanks & best regards,
Banibrata Dutta

-----Original Message-----
From: owner-cxx-dev@cxx.cup.hp.com [mailto:owner-cxx-dev@cxx.cup.hp.com] On
Behalf Of Vuppula, Himabindu
Sent: Thursday, September 15, 2005 6:33 AM
To: hpux-devtools@cxx.cup.hp.com; cxx-dev@cxx.cup.hp.com
Subject: CXX-DEV: Request for Requirements for the WDB debugger

Folks,

Following the release of HP WDB 5.2 debugger (hp.com/go/wdb), the HP
debugger team is in the process of finalizing the plans for the next major
release of the HP-UX debugger.  If you have a favorite feature that is
preventing WDB to become your favorite debugger, or are aware of outright
bugs that get in the way of finding your own bugs, this would be a very good
time to send us a note.

To be of help in this planning exercise, please send us your input (to
<wdb-help@cup.hp.com>) by Monday September 19.

Bug reports would be particularly welcome and while we can't promise to act
on all enhancement requests, we usually give (much) higher priority to user
reported problems and feature requests compared to other requirements that
we have come up with !

Thanks,
HP WDB Team
 _________________________________________________________________
 To leave this mailing list, send mail to majordomo@cxx.cup.hp.com
    with the message UNSUBSCRIBE cxx-dev
_________________________________________________________________
 _________________________________________________________________
 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]