GNU bug report logs - #16570
24.2; emacs ediff-directories segmentation fault

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 16570 in the body.
You can then email your comments to 16570 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "S. Gimeno Garcia" <sebastian.gimenogarcia <at> dlr.de>
To: <bug-gnu-emacs <at> gnu.org>
Subject: 24.2; emacs ediff-directories segmentation fault
Date: Mon, 27 Jan 2014 11:43:09 +0100

Hi,

During a ediff-directories session, comparing subdirectories
recursively, and after some successfully "ediff" of files in the
directories, emacs suddenly crashes with a segmentation fault.

This behavior occurred often lately, but unfortunately I haven't
succeeded to reproduce the crash in a controlled way to provide
more detailed information.

Best regards,
Sebastian


In GNU Emacs 24.2.1 (x86_64-suse-linux-gnu, GTK+ Version 3.4.4)
of 2012-10-10 on build20
Windowing system distributor `The X.Org Foundation

Message #8 received at 16570 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: "S. Gimeno Garcia" <sebastian.gimenogarcia <at> dlr.de>
Cc: 16570 <at> debbugs.gnu.org
Subject: Re: bug#16570: 24.2; emacs ediff-directories segmentation fault
Date: Mon, 27 Jan 2014 12:31:32 -0500

"S. Gimeno Garcia" wrote:

> In GNU Emacs 24.2.1 (x86_64-suse-linux-gnu, GTK+ Version 3.4.4)
> of 2012-10-10 on build20

Does SUSE provide a debug package for Emacs, or can you build Emacs yourself?
If the latter, please fetch the 24.3 (note not 24.2) sources, configure
emacs using

CFLAGS="-O0 -g3" ./configure [...]
make

cd src
# You may need to modify "auto-load safe-path" in ~/.gdbinit - see
# etc/DEBUG in the Emacs sources.
gdb ./emacs
run

and if/when it crashes, send the result of "bt full" here.

Without a backtrace, or reproducible crash recipe, nothing can be done.

Thanks.

Message #11 received at 16570 <at> debbugs.gnu.org (full text, mbox):

From: "S. Gimeno Garcia" <sebastian.gimenogarcia <at> dlr.de>
To: Glenn Morris <rgm <at> gnu.org>
Subject: Re: bug#16570: 24.2; emacs ediff-directories segmentation fault
Date: Tue, 28 Jan 2014 14:39:02 +0100

Hi,

Thanks for the rapid response!

Actually, I cannot reproduce the error again. Between last friday and 
yesterday, the emacs crash happened about 4 or 5 times, always during a 
ediff-directories session.
However, I cannot  reproduce in a controlled way the conditions that 
lead to the crash, so I cannot send you any backtrace, or reproducible 
crash recipe :(
If I find a way to do it, I'll come back to you.

Cheers,
Sebastian

On 01/27/2014 06:31 PM, Glenn Morris wrote:
> "S. Gimeno Garcia" wrote:
>
>> In GNU Emacs 24.2.1 (x86_64-suse-linux-gnu, GTK+ Version 3.4.4)
>> of 2012-10-10 on build20
> Does SUSE provide a debug package for Emacs, or can you build Emacs yourself?
> If the latter, please fetch the 24.3 (note not 24.2) sources, configure
> emacs using
>
> CFLAGS="-O0 -g3" ./configure [...]
> make
>
> cd src
> # You may need to modify "auto-load safe-path" in ~/.gdbinit - see
> # etc/DEBUG in the Emacs sources.
> gdb ./emacs
> run
>
> and if/when it crashes, send the result of "bt full" here.
>
> Without a backtrace, or reproducible crash recipe, nothing can be done.
>
> Thanks.
>

Message #14 received at 16570 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: "S. Gimeno Garcia" <sebastian.gimenogarcia <at> dlr.de>
Cc: Glenn Morris <rgm <at> gnu.org>, 16570 <at> debbugs.gnu.org
Subject: Re: bug#16570: 24.2; emacs ediff-directories segmentation fault
Date: Sat, 26 Dec 2015 13:58:57 +0100

"S. Gimeno Garcia" <sebastian.gimenogarcia <at> dlr.de> writes:

> Actually, I cannot reproduce the error again. Between last friday and
> yesterday, the emacs crash happened about 4 or 5 times, always during
> a ediff-directories session.
> However, I cannot  reproduce in a controlled way the conditions that
> lead to the crash, so I cannot send you any backtrace, or reproducible
> crash recipe :(
> If I find a way to do it, I'll come back to you.

More information was requested, but no response was given within a few
months, so I'm closing this bug report.  If the problem still exists,
please reopen this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.