ports/114993: Emacs causes SIGSEGV
Gardner Bell
gbell72 at rogers.com
Mon Jul 30 12:10:08 UTC 2007
The following reply was made to PR ports/114993; it has been noted by GNATS.
From: Gardner Bell <gbell72 at rogers.com>
To: Giorgos Keramidas <keramida at freebsd.org>
Cc: bug-followup at freebsd.org
Subject: Re: ports/114993: Emacs causes SIGSEGV
Date: Mon, 30 Jul 2007 07:33:45 -0400 (EDT)
--- Giorgos Keramidas <keramida at freebsd.org> wrote:
> On 2007-07-28 17:58, Gardner Bell <gbell72 at 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 at 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.
>
I just rebuilt emacs about an hour ago WITHOUT_GTK and it is working as
intended now. Should I file a big report to emacs-devel as well with
the backtrace I submitted here or will I need to add debug symbols
first?
More information about the freebsd-ports-bugs
mailing list