On Monday 24 Oct 2011 00:06:21 Alex Schuster wrote:
> András Csányi writes:
> > I'm an average Amarok user and experiencing a random segfault I
> > decided that I would like to report it. I know I have to recompile
> > Amarok with debug flag but I'm not sure it is enough. Can you tell me
> > what is needed more?
>
> No, I think the debug USE flag has another purpose.
> You need to add '-gddb' to you CFLAGS in make.conf, and make sure that
> 'nostrip' or better 'splitdebug' is in your FEATURES list (the debug
> code added by -gddb would be stripped away if not). This will get you a
> useful backtrace in DrKonqui, if you are using KDE.
>
> > By the way, these reports should be send for the
> > Amarok developers not gentoo guys, shouldn't they?
>
> I would say so, but I'm not entirely sure. It's easier this way, but
> there's a slight chance that the problem is Gentoo-specific.
>
> Wonko
Also if you dont want to do thos globbaly for all your packages you can make
use of /etc/portage/env/.
For example this is what i have for amarok in
/etc/portage/env/media-sound/amarok
CFLAGS="-march=core2 -O1 -g"
CXXFLAGS="${CFLAGS}"
FEATURES="splitdebug"
also note when doing it this way, you will also have to do this for a few
dependencies that amarok uses. The way i did it was, When dr konqi pops up
after amarok crashes, it displays a list of files needed for a more usefull
backtrace (in the developer information tab).Use equery to find out which
packages those files belong to and add an entry in /etc/portage/env for them.
After thats done rebuild those pacakges.
--
- Yohan Pereira
"A man can do as he will, but not will as he will" - Schopenhauer
