| Summary: | qtiplot-0.9.7.7 segmentation faults at start-up | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | urcindalo <urcindalo> |
| Component: | Current packages | Assignee: | Marcus D. Hanwell (RETIRED) <cryos> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | sci |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
urcindalo
2009-07-10 10:40:44 UTC
Thank you for report. To shed more light on this issue, please, try to rebuild qtiplot (and probably you'll need to build some dependencies too) with debugging symbols and show us backtrace: http://www.gentoo.org/proj/en/qa/backtraces.xml Or.. does maintainers has better idea what's going on here? Thanks for the info and the help. I appreciate it. I re-emerged every dependency and then qtiplot with -ggdb set in my /etc/make.conf. To my susprise, when I started qtiplot again the segmentation fault was gone for good. Why? I really don't know. I think the only dependency I hadn't re-emerged before was boost, because it is a big package and other packages depending on it, like openoffice, were working OK. This time I did re-emerge it as well as all the other dependencies and qtiplot worked afterwards, as I said. So, it seems whatever was causing the segfault is now gone. But, why didn't revdep-rebuild catch the problem in the first place? I think this bug may be marked as SOLVED :) |