Date: Mon, 30 Jul 2007 12:20:06 GMT From: Giorgos Keramidas <keramida@freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/114993: Emacs causes SIGSEGV Message-ID: <200707301220.l6UCK6YM047368@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 15:15:33 +0300 On 2007-07-30 07:33, Gardner Bell <gbell72@rogers.com> wrote: >--- Giorgos Keramidas <keramida@freebsd.org> wrote: >>> #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? It may be worth building a snapshot of GNU Emacs yourself, and running Emacs 22 inside GDB. Then, when Emacs crashes, you will be able to debug the live process, not just a core dump. More instructions about building Emacs with debugging symbols and running it under GDB can be found at the source of Emacs itself. Ultimately, it should be possible to gather a stack trace of the crashed Emacs process, a Lisp backtrace of Emacs itself, and then we should notify the emacs-devel mailing list with the results. The memory allocation of GNU Emacs 22 and the FreeBSD 7.0-CURRENT malloc() haven't played nicely with each other for several months, but it is difficult to track down exactly why GTK+ widgets trigger this so easily... Please, make sure you Cc: me in any emails posted to emacs-devel, as this GTK+-triggered Emacs crash has been of interest to me for some time. - Giorgos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707301220.l6UCK6YM047368>