|
From: smiley g. <smi...@ya...> - 2004-07-09 06:03:54
|
Hi friends, I had my application almost up and running with valgrind, when the admins upgraded my Linux machine to RedHat Linux AS 3 upgrade 2. I am facing a hang and I have no clue where its happening. The application starts numerous daemon processes and involves interaction among these daemon processes. I am not able to attach a debugger to these processes when valgrind is involved and --db-attach doesn't work with fork'd processes yet. Can somebody give me a clue about how to attach debugger to a daemon process and get to see code in the debugger. when i do a backtrace I only see a list of addresses and addr2line utility doesn't give me anything new. or anybody seeing anything new with upgrade 2 ? or anybody knows is valgrind uses pipes internally ? for I know that my application doesn't use pipes but /proc/pid/fd lists a few pipes ??? Thanks a lot in advance, Madhan. __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail |
|
From: Nicholas N. <nj...@ca...> - 2004-07-09 08:12:31
|
On Thu, 8 Jul 2004, smiley glitter wrote: > or anybody knows is valgrind uses pipes internally ? > for I know that my application doesn't use pipes but > /proc/pid/fd lists a few pipes ??? Valgrind 2.1.0 and later do use pipes. I can't help with your other questions, sorry. N |