Bug 811369

Summary:	segfault kcachegrind
Product:	[Fedora] Fedora	Reporter:	la_antorcha_guia
Component:	kdesdk	Assignee:	Than Ngo <than>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	jreznik, kevin, ltinkl, mbriza, rdieter, rnovacek, smparrish, than
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-27 13:15:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description la_antorcha_guia 2012-04-10 20:06:14 UTC

Description of problem:
segfault

Version-Release number of selected component (if applicable):


How reproducible:
load file, press F5

Steps to Reproduce:
1.load file
2.press F5
3.segfault
  
Actual results:
segfault

Expected results:
reload

Additional info:

Comment 1 Martin Bříza 2012-04-26 12:18:47 UTC

I wasn't able to reproduce this on my box, can you please provide more information about versions of components used when the crash appeared?
More details about the event itself (as the file analyzed, if the program has been ran on a clean system after restart and everything else that could come to your mind) would be highly appreciated.
Thank you.

Comment 2 la_antorcha_guia 2012-04-26 13:36:36 UTC

kdesdk-kcachegrind-4.8.2-2.fc16.x86_64

Linux * 3.3.2-1.fc16.x86_64 #1 SMP Sat Apr 14 00:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux


For me with this steps bug appears:
1.Open program
2.Load file
3.Modify file with new data, external program (example: xdebug)
4.press F5
5. Crash!

Regards,

Comment 3 Martin Bříza 2012-04-26 13:47:43 UTC

Please, can you attach some minimal example of the processed log before and after change with which the crash still happens? 
I tried replacing whole contents of a callgrind log while being opened in kcachegrind with another one and it didn't crash.
Also, a backtrace with debug information would be appreciated.
Thanks.

Comment 4 la_antorcha_guia 2012-04-26 16:01:25 UTC

Good news,

After try to reproduce it again, seems that work without any problem.

Thanks,

Comment 5 Jaroslav Reznik 2012-04-27 13:15:38 UTC

Ok, 
it's great it works. I'm going to close the report as we do not have enough date (no backtrace, no reproducer) and seems like it's not reproducible. Feel free to open the report in case of reoccurrence and attach requested data.