On 2/28/07, Bo Ørsted Andresen <[EMAIL PROTECTED]> wrote:
On Wednesday 28 February 2007 11:30:23 Mark Knecht wrote:
> Thanks. Yes, I'm completely through the emerge -DuN world,
> revdep-rebuild process. No help there. Evolution continues to crash.
> We were running Evolution 2.4. Unfortunately it's no longer in
> portage. I've built every unmasked and masked version in portage and
> they all crash. BugBuddy pops up but the backtrace is useless since
> there is no debugging info. I'm going to rebuild the who machine from
> scratch (emerge -e system, emerge -e world) to see if I get lucky.
You have realized that you need to use either FEATURES=nostrip or
FEATURES=splitdebug to get a better backtrace? Adding "-g" to your CFLAGS
wouldn't hurt either.
--
Bo Andresen
Thanks Bo. I read through the backtrace page you pointed me at and
decided I didn't understand enough of it to correctly get through it.
As a result I'm making no attempt at this point to get a back trace.
I'm just rebuilding everything on time to see if Evolution starts
working. I'm done with emerge -e system and about 1/3 of the way
through emerge -e world so maybe this evening I'll know the results of
that.
If it still fails then I'll have to return here one more time to ask
questions about what needs to be rebuilt. Must I rebuild everything or
can I just do Evolution and see if it drops into a library and then
rebuild that library and go deeper?
I have no desire to rebuild the complete system just to find a bug in
a program my dad doesn't really care if he's running only to find that
like a number of bug reports I'm made recently I never get a response
and there was no reason to do all the work on my end.
Cheers,
Mark
--
gentoo-user@gentoo.org mailing list
