search

qchbai / gperftools

Automatically exported from code.google.com/p/gperftools
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Hangs on RHel5 Machine on system calls #426

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. write code which has system call and fork calls
2. run on a Red Hat EL5 machine
3. hangs on all the system calls with the stack trace as 

#0  0xffffe410 in __kernel_vsyscall ()
#1  0x00c00c82 in do_system () from /lib/libc.so.6
#2  0x00c01062 in system () from /lib/libc.so.6
#3  0x00d231cd in system () from /lib/libpthread.so.0

the machine used is 

Linux dz7 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64 
x86_64 GNU/Linux

when i run the same binary on a different machine it runs fine; the machine on 
which it runs fine is Linux tangent 2.6.9-89.ELlargesmp #1 SMP Mon Apr 20 
10:43:12 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

What is the expected output? What do you see instead?
It should not hang

What version of the product are you using? On what operating system?
google profiler version is 1.9.1 and OS version is updated in the section above

Original issue reported on code.google.com by anshulkr on 23 Apr 2012 at 7:17

GoogleCodeExporter commented 9 years ago 
Any further update here? Is that a complete backtrace?

Original comment by chapp...@gmail.com on 3 May 2012 at 3:06

GoogleCodeExporter commented 9 years ago 
no this is not the complete stack trace, but this happens every time we try do 
a fork or system call. I tried compiling the entire code on RHEL5 with the 
application and google profiler. this seems to work fine, but the should not be 
needed.

Original comment by anshulkr on 8 May 2012 at 5:08

GoogleCodeExporter commented 9 years ago 
Can you clarify. When you compiled on RHEL5 did it work for you? as opposed to 
using the prebuilt package?

Original comment by chapp...@gmail.com on 11 Mar 2013 at 1:12

GoogleCodeExporter commented 9 years ago 
Please, consider testing on latest svn. Some fixes for fork were merged 
recently.

Original comment by alkondratenko on 6 Jul 2013 at 11:46

GoogleCodeExporter commented 9 years ago 
Going to assume it's fixed given lack of activity and probable fix merged 
before 2.1 release

Original comment by alkondratenko on 14 Sep 2013 at 8:34

GoogleCodeExporter commented 9 years ago 
Sorry for the late reply but with the latest release we are not facing this 
issue while running the CPU profiler on RHEL 5.

Original comment by anshulkr on 23 Sep 2013 at 3:43

GoogleCodeExporter commented 9 years ago 
I can still see the same issue of hanging even with the latest version 2.2.1 of 
google cpu profiler.
The pstack shows the same do_system () hanging issue.

Original comment by rajdeep....@gmail.com on 18 Aug 2014 at 9:41

GoogleCodeExporter commented 9 years ago 
Assuming that you've filed issue-642 for that. Will investigate as part of new 
ticket. There's great chance that it's indeed something new.

Original comment by alkondratenko on 18 Aug 2014 at 3:50