Umesh Sisodia <usisodia@xxxxxxxxxxx> writes: > Hi Dave, > > Thanx for your time. > Ya, its a C++ aplication. I am sure it is not forking any child. > It is not waiting, infact it is consuming lots of CPU time. It sounds like you have an infinite loop. Can't you run it under gdb, rather than attaching to it? Alternatively, try to make it dump core by sending it a QUIT signal. You can then use gdb "post mortem" to investigate where the program was executing when the signal arrived. This method will require you to raise your coredumpsize limit above the Red Hat default (which is 0). -- tim writer <tim@xxxxxxxxxxx> starnix inc. tollfree: 1-87-pro-linux thornhill, ontario, canada http://www.starnix.com professional linux services & products _______________________________________________ Redhat-devel-list mailing list Redhat-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/redhat-devel-list
