Brian Reichert wrote:
On Fri, Oct 15, 2004 at 10:46:01AM +0800, victor wrote:I haven't tried -v before, let me give it a try next time and see what it returns.
As root I ran /usr/bin/strace -p <httpd process eating up all cpu>How are you invoking strace?
There are other useful arguments to strace; see the manpage for '-f -F -v', and so forth.
sadly adding debug code in the source in advance is not quite an option for me, since the problem we have enocunted is an unexpected one. but gdb is definitily a good idea, I will give it a shoot.We have sorted out the problem on this part it turns out to be a special case which casued one of the regex run into infinite loop, so no system call hads been made at all.
I just wonder is there any other tool out that beside strace I can use in such situtation?
You can use gdb and friends to attach to a process, but that's more
useful if you've got debugging complied into your code.
ah! this sound like what I have been looking for, using lsof on the descriptors in question, this should tell me a lot on those mystery descriptor, I wonder why I didn't though of this before.. ^^! thanks brian, this is most useful.I am sorry I did not save a copy of the lsof output. but is there any specific detail you are looking for/I should pay extra attention?
I tend to _not_ use /proc, and was hoping you would have the
opportunity to point lsof at the descriptors in question; this is
just in case there was a latency-induced flaw in terms of what
details /proc was exposing.
Thank you very much Brian, you gave me lots of good tips, i will check them all out, again thank you. ^^
Tor.
-- <!--------------------------------------------- Victor Development Engineer Outblaze Ltd ---------------------------------------------->
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
