Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 130601 - Ark 3.5.2 crashes on closing
Summary: Ark 3.5.2 crashes on closing
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Highest major (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-20 06:33 UTC by Alessandro Calorì
Modified: 2006-04-21 16:18 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Backtrace messages (ark-crash,1.62 KB, text/plain)
2006-04-20 06:35 UTC, Alessandro Calorì 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alessandro Calorì 2006-04-20 06:33:54 UTC 
Testing Ark version (3.5.2) crashes all the time on closing.
Comment 1 Alessandro Calorì 2006-04-20 06:35:47 UTC 
Created attachment 85032 [details]
Backtrace messages

These are the backtrace messages that KDE gives. The signal code of crash is 6 (SIGABRT).
Comment 2 Carsten Lohrke (RETIRED) gentoo-dev 2006-04-21 12:35:57 UTC 
A backtrace without symbol information is useless. But please test if kdelibs-3.5.2-r4 fixes the problem for you.
Comment 3 Alessandro Calorì 2006-04-21 16:05:45 UTC 
(In reply to comment #2)
> A backtrace without symbol information is useless.

Tes, I know but how can I provide such information?

> But please test if kdelibs-3.5.2-r4 fixes the problem for you.

Yes, it does! I've just updated it and there is not any problem...
Comment 4 Carsten Lohrke (RETIRED) gentoo-dev 2006-04-21 16:18:26 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > A backtrace without symbol information is useless.
> 
> Tes, I know but how can I provide such information?

You have to emerge the affected application (and its dependencies as necessary) with USE=debug FEATURES=nostrip and without -fomit-frame-pointer in your compiler flags.

> Yes, it does! I've just updated it and there is not any problem...

The it was the faulty patch I managed to pick up with -r3.