Debugging with gdb in Tuxedo

[David Black_5]

Hi, how would one of our developers debug a
Tuxedo server binary using gdb, does he call gdb in the BBL file and force reporting out to a file, he is trying to find a memory leak.
Is the Tuxedo start going to work.
Thanks for any help
Dave Black

[Muthukumar_5]

IF any executable binary contains with debugging symbols then we can start to debug it out with gdb.

We can gdb for debugging memory leak(s).
Depends upon the platform on hp-ux (pa-risc / ipf) we have to link libraries to get memory leak details.

You can refer ,
http://devrsrc1.external.hp.com/devresource/Tools/wdb/doc/guide/gdb_15.html

for memory leak debugging.

You can transer the information of gdb to another file as,


#script filename
# gdb
gdb> ..
gdb> quit
# exit

Now all informations gdb will be in filename

else,

# gdb | tee filename
gdb> ..
gdb> quit

Now filename will contains the informations of gdb actions

Debugging is used to find the fault behaviour in the binary and analyse stack trace so that we can get good performing sources.

[David Black_5]

Hi Muthukumar, thanks but I think you misunderstood my question. Yes we can gdb any
debug compiled binary, but Tuxedo controls
the startup of this code along with other
partner server code. The question is can
we modify the Tuxedo startup to di as you state and output the memory leak report to a file when our testing has ended.
Thanks,
Dave Black