Summary: | app-arch/kdar segfaults if gcc-profile set to 3.4.3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Ruskin <aoyu93> |
Component: | Current packages | Assignee: | MATSUU Takuto (RETIRED) <matsuu> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2004.3 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Ruskin
2004-11-21 11:51:53 UTC
1.3.0 is out, maybe a simple bump fixes the problem 1.3.0 in cvs. thanks. It isn't fixed! With KDar 1.3.0 compiled with gcc-3.4.2: When opening an archive created in version 1.2.0... Dr. Konqui says: KDar crashed and caused signal 11 Backtrace: This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. Using host libthread_db library "/lib/libthread_db.so.1". After setting gcc to 3.3.4 and remerging kdar-1.3.0 it works fine. Hi!
>It isn't fixed! With KDar 1.3.0 compiled with gcc-3.4.2:
I have problems in emerging kdar on amd64 and submitted bugreport (see #70249).
With kdar-1.3.0 the same situation - configure does not find qt.
Any hint?
Sincerely,
Gour
Closing an obsolete bug, kdar-1* is no longer in portage. |