Date: Sat, 19 Jul 2003 23:40:30 -0700 From: "Craig Riter" <criter@riter.com> To: "'Joe Marcus Clarke'" <marcus@marcuscom.com> Cc: freebsd-gnome@freebsd.org Subject: RE: debugging gnucash segmentation fault Message-ID: <001201c34e89$d113d5d0$cbffa8c0@EOS2> In-Reply-To: <1058680953.35075.4.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry, I should have said that this happens at start up of the application. I don't get anything, not even the little splash screen about it loading. To double check everything I started a recursive rebuild of everything with this command... $portupgrade -Rf gnucash If that doesn't fix it, is there an easy way to have it reinstall everything with symbols? Would this command work? $portupgrade -m "STRIP= CFLAGS=\"-O -pipe -g\" -iRf gnucash I figure the -i will ask which ports should be re-installed with symbols or maybe I shouldn't even bother and just install everything with symbols. Thanks again, Craig -----Original Message----- From: Joe Marcus Clarke [mailto:marcus@marcuscom.com] Sent: Saturday, July 19, 2003 11:03 PM To: Craig Riter Cc: freebsd-gnome@freebsd.org Subject: Re: debugging gnucash segmentation fault On Sun, 2003-07-20 at 01:39, Craig Riter wrote: > I have been trying to debug a problem with gnucash on my FreeBSD box. I am > running FreeBSD 4.8-STABLE and had rebuilt my system on June 30. I have > attached a list of my current ports. Everything that gnucash depends meets > the dependencies or has been upgrade past the dependent version. > > After gnucash seg faults in guile I started up the gdb and got the stack > trace (also attached). > > I did have everything working before with version 1.8.2 or was it .1. I > don't remember exactly just that it used to work. I am not sure where to go > next with this. Does anyone have in ideas of how to figure out exactly what > is causing my problem? You need to rebuild gnucash, and all of its dependencies with debugging symbols, then redo the stack trace. Only then will it be useful. It would also be helpful to know exactly the steps you did to reproduce the crash. Joe [message trimmed]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001201c34e89$d113d5d0$cbffa8c0>