Date: Tue, 01 Jun 2004 22:18:22 -0700 From: Sean McNeil <sean@mcneil.com> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: freebsd-amd64@freebsd.org Subject: Re: core dumps with bash, nautilus, and gnome-vfs-daemon Message-ID: <1086153502.41019.4.camel@server.mcneil.com> In-Reply-To: <1086152746.21857.12.camel@shumai.marcuscom.com> References: <1086152406.1411.12.camel@server.mcneil.com> <1086152746.21857.12.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
sorry for the dup, but want to make sure it goes out the othe right mailing lists. I had a typo before.... On Tue, 2004-06-01 at 22:05, Joe Marcus Clarke wrote: > On Wed, 2004-06-02 at 01:00, Sean McNeil wrote: > > This happens with -CURRENT and all recent ports built on an amd64 arch. > > I have the core files and will do a trace when I get a working debugger. > > > > bash core dumps when I resize a gnome-terminal window. > > > > gnome-vfs-daemon and nautilus core dump when I try to start nautilus. > > If I do it from a gnome-terminal, I get the following output: > > > > nautilus in free(): error: junk pointer, too high to make sense > > nautilus in malloc(): error: recursive call > > nautilus in malloc(): error: recursive call > > Abort trap (core dumped) > > These are standard malloc issues. If you do ln -s aj /etc/malloc.conf, > do these crashes go away? > > Joe When I do that, I no longer get core, but I get nautilus nautilus in free(): warning: junk pointer, too high to make sense nautilus in free(): warning: junk pointer, too high to make sense and then the application error dialog asking to restart, close, or send report. Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1086153502.41019.4.camel>