Date: Mon, 30 Jul 2007 00:50:07 GMT From: Giorgos Keramidas <keramida@freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/114993: Emacs causes SIGSEGV Message-ID: <200707300050.l6U0o7Ed099430@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/114993; it has been noted by GNATS. From: Giorgos Keramidas <keramida@freebsd.org> To: Gardner Bell <gbell72@rogers.com> Cc: bug-followup@freebsd.org Subject: Re: ports/114993: Emacs causes SIGSEGV Date: Mon, 30 Jul 2007 03:21:58 +0300 On 2007-07-28 17:58, Gardner Bell <gbell72@rogers.com> wrote: > >Number: 114993 > >Category: ports > >Synopsis: editors/Emacs causes SIGSEGV > FreeBSD home.bsdca.com 7.0-CURRENT FreeBSD 7.0-CURRENT #3: Thu Jul 26 > 15:29:51 EDT 2007 root@home.bsdca.com:/usr/obj/usr/src/sys/HOME > i386 > > >Description: > While editing any plain text file in emacs version 22.1.1 I receive > the following SIGSEGV with partial backtrace. > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x8351000 (LWP 100062)] > 0x08182d6c in calloc () > (gdb) where > #0 0x08182d6c in calloc () > #1 0x08183067 in free () > #2 0x081316c8 in abort () > #3 0x08183057 in free () > #4 0x288ad98b in g_slice_get_config () from /usr/local/lib/libglib-2.0.so.0 This looks similar to crashes I've reported to the emacs-devel mailing list for Emacs 22. The crashes go away if onee rebuilds WITHOUT_GTK for me on FreeBSD 7.0-CURRENT. Can you try building the port without a GTK+ interface and see if the crash persists? If not, we have to collect enough information for the upstream Emacs development team, to be able to fix this either with a local FreeBSD-specific patch or by fixing the Emacs 22.X source tree itself in the Emacs CVS repository.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707300050.l6U0o7Ed099430>