Bug 253523

Summary:	cachegrind crashes at m_signals.c:2332
Product:	[Developer tools] valgrind	Reporter:	Yuri <yuri>
Component:	cachegrind	Assignee:	Nicholas Nethercote <njn>
Status:	RESOLVED FIXED
Severity:	major	CC:	jseward, pjfloyd
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Yuri 2010-10-07 17:52:45 UTC

When I run my project through callgrind I get the message (below).
I run on Ubuntu, installed valgrind from the standard in Ubuntu Debian package.
valgrind-3.6.0.SVN-Debian

No errors were reported by valgrind prior to this error.
Also it doesn't seem to be related to m_mallocfree.c.

==22303==
==22303== Events    : Ir Dr Dw I1mr D1mr D1mw I2mr D2mr D2mw AcCost1 SpLoss1 AcCost2 SpLoss2
==22303== Collected : 24729027675 8872656740 5027580442 143222545 92267220 29410392 33874489 42213804 17081489 57117142887 9079166687 15957487164 2776774296
==22303==
==22303== I   refs:      24,729,027,675
==22303== I1  misses:       143,222,545
==22303== L2i misses:        33,874,489
==22303== I1  miss rate:           0.57%
==22303== L2i miss rate:           0.13%
==22303==
==22303== D   refs:      13,900,237,182  (8,872,656,740 rd + 5,027,580,442 wr)
==22303== D1  misses:       121,677,612  (   92,267,220 rd +    29,410,392 wr)
==22303== L2d misses:        59,295,293  (   42,213,804 rd +    17,081,489 wr)
==22303== D1  miss rate:            0.8% (          1.0%   +           0.5%  )
==22303== L2d miss rate:            0.4% (          0.4%   +           0.3%  )
==22303==
==22303== L2 refs:          264,900,157  (  235,489,765 rd +    29,410,392 wr)
==22303== L2 misses:         93,169,782  (   76,088,293 rd +    17,081,489 wr)
==22303== L2 miss rate:             0.2% (          0.2%   +           0.3%  )
--22303-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
--22303-- si_code=1;  Faulting address: 0x5DB7BF8C;  sp: 0x671b3228

valgrind: m_signals.c:2332 (sync_signalhandler_from_kernel): Assertion 'tid != 0' failed.
==22303==    at 0x3801D5A5: report_and_quit (m_libcassert.c:191)

sched status:
  running_tid=2


  Note: see also the FAQ in the source distribution.
  It contains workarounds to several common problems.
  In particular, if Valgrind aborted or crashed after
  identifying problems in your program, there's a good chance
  that fixing those problems will prevent Valgrind aborting or
  crashing, especially if it happened in m_mallocfree.c.

  If that doesn't help, please report this bug to: www.valgrind.org

  In the bug report, send all the above text, the valgrind
  version, and what OS and version you are using.  Thanks.

  Command exited with non-zero status 1
  258.24user 1751.00system 33:30.32elapsed 99%CPU (0avgtext+0avgdata 1320336maxresident)k
  9208inputs+126760outputs (142major+194556minor)pagefaults 0swaps

Comment 1 Julian Seward 2010-10-07 19:13:15 UTC

Just to double check, this is with cachegrind or callgrind?  You
selected cachegrind as the "Component", but we recently fixed a bug
that sounds very similar to this in callgrind, and the output looks
like it comes from callgrind, not cachegrind.

Can you try again with the valgrind svn trunk and see if the problem
is still there?  It is easy to check out and build, for instructions
see

http://www.valgrind.org/downloads/repository.html

Comment 2 Yuri 2010-10-07 19:43:11 UTC

Sorry, it's about callgrind tool.
I will try again with the trunk and will post the results here.

Comment 3 Yuri 2010-10-07 21:05:55 UTC

You are right, issue is fixed in the current trunk.

Comment 4 Paul Floyd 2025-09-09 19:09:06 UTC

Last thing was that this is fixed so closing it.