| 1 |
On Fri, May 6, 2011 at 10:28 AM, Lorenzo Marussi <info@××××××××××××××.it> wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> thank you for your reply, |
| 5 |
> |
| 6 |
> I check that I didn't mixed QT version, |
| 7 |
> first I tried with 4.7.2, than I unmerged all qt packages and I tried 4.7.3 |
| 8 |
> . |
| 9 |
> every time after emerging I checked system consistency with revdep-rebuild. |
| 10 |
> |
| 11 |
> Now I unmerged all, emerged all QT packages (4.72) with "debug" use, but I |
| 12 |
> haven't got any other message than: |
| 13 |
|
| 14 |
Hi, |
| 15 |
|
| 16 |
The debug USE flag is for enabling debug features in a package, not |
| 17 |
really the same thing I was talking about. In /etc/make.conf you need |
| 18 |
to change your CFLAGS to include -ggdb and reduce optimization to -O1. |
| 19 |
Then you need to add "nostrip" into your FEATURES, otherwise that |
| 20 |
debugging data would get stripped as part of the install process of |
| 21 |
emerge. |
| 22 |
|
| 23 |
After you made those changes, emerge anything that you want to get a |
| 24 |
backtrace from. Now you should be able to see better info when it |
| 25 |
crashes, run it in gdb and see source code line numbers and all the |
| 26 |
good stuff like that. :) |
| 27 |
|
| 28 |
If the crashes get to a place where you don't have debug info, if it |
| 29 |
is crashing in another dependency perhaps, you might need to emerge |
| 30 |
other packages with the debugging info as well. Maybe glibc... |
| 31 |
|
| 32 |
For more information please read this page: |
| 33 |
http://www.gentoo.org/proj/en/qa/backtraces.xml |
| 34 |
|
| 35 |
I hope that helped. Good luck! |
Archives