search

cynthia / gperftools

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

Disabling profiler because SIGPROF handler is already in use. #393

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I got this warning when I use profile on my virtual machine of 
“2.6.18-274.12.1.el5xen #1 SMP Tue Nov 29 14:18:21 EST 2011 x86_64 x86_64 
x86_64 GNU/Linux”.
But I didn't install SIGPROF handler myself, I debug my main and sigation()the 
SIGPROF, I Got this:
$2 = {__sigaction_handler = {sa_handler = 0x37ec4d62c0 <profil_counter>, 
sa_sigaction = 0x37ec4d62c0 <profil_counter>}, sa_mask = {__val = 
{18446744073709289215, 46909632806913, 140737488344672, 
      4131212846, 140737488345072, 240186842448, 46912498377520, 0, 4294967295, 240199406976, 46912498372608, 9830400, 4294967295, 140737488345336, 9924248, 0}}, sa_flags = 335544320, 
  sa_restorer = 0x37ec4302d0 <__restore_rt>}

I do not install profil_counter myself, and why I got the warning? any help?

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by thunder5...@gmail.com on 11 Jan 2012 at 12:15

GoogleCodeExporter commented 9 years ago 
I'm afraid I don't know who else might be installing a sigprof handler on your 
machine.  Did a web serach for profil_counter turn up anything useful?

Closing this since it's not a tcmalloc bug.  Not sure there's much we can do to 
help.

Original comment by csilv...@gmail.com on 12 Jan 2012 at 11:45