Summary: | Juk crashes on startup due to glibc memory error | ||
---|---|---|---|
Product: | [Applications] juk | Reporter: | Fabio Junior Sabai <fjsabai> |
Component: | general | Assignee: | Scott Wheeler <wheeler> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Fabio Junior Sabai
2005-12-20 17:26:26 UTC
Did you also upgrade your compiler recently? Things like this usually happen after upgrading GCC without upgrading C++ libraries (such as taglib or libtunepimp). Can you valgrind JuK? Or run it in gdb and give us the backtrace of the moment glibc shows that error message? If it is memory corruption valgrind would be the most useful by far. gdb is likely to be unable to determine the correct backtrace. At least this is judging from my investigations into the last JuK bug revealed by the glibc memory corruption monitor. Well, I upgraded libtunepimp and libmusicbrainz and now juk works fine. Thanks all. |