Bug 162103

Summary:	callgrind crash with trace
Product:	[Developer tools] valgrind	Reporter:	Aleks Totic <a>
Component:	callgrind	Assignee:	Josef Weidendorfer <josef.weidendorfer>
Status:	RESOLVED WAITINGFORINFO
Severity:	crash	CC:	christoph
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Trace of the crash

Description Aleks Totic 2008-05-14 20:20:12 UTC

Version:           valgrind-3.3.0-Debian (using Devel)
Installed from:    Compiled sources
Compiler:          gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)  
OS:                Linux

I am trying to profile a debug version of mobile firefox. The program starts with:

valgrind --trace-children=yes --tool=callgrind --instr-atstart=no  ./tip/obj-xr-dbg/dist/bin/xulrunner ./fennec/touch/application.ini 

and crashes with an assert in callgrind code. The annoying part is that the crash is only 90% reproducible. If I crash once, I've never been able to run it again without a crash. But, if I reboot, I can get lucky and get a few runs in before it crashes again.

I was able to work around the crash by commenting out the call to gnome_vfs_mime_get_default_application in my code. Noticed it on the stack on every crash, so I just gave it a shot.

BTW, valgrind is awesome! I have not had to do heavy duty profiling in a few years, and this is so much better than what we used to do.

Comment 1 Aleks Totic 2008-05-14 20:20:59 UTC

Created attachment 24768 [details]
Trace of the crash

Comment 2 Josef Weidendorfer 2008-05-15 19:57:33 UTC

Is this on x86? Any chance for me to reproduce?

Comment 3 Aleks Totic 2008-05-15 21:04:40 UTC

It is on x86. No chance for you, but I'll be happy to run any tests you might need.

Comment 4 Christoph Cullmann 2024-05-10 22:32:35 UTC

Please re-open if one can reproduce this with a recent version, thanks!