GNU bug report logs - #9723
24.0.50; Emacs Clipboard crash

Previous Next

Package: emacs;

Reported by: Joseph Jones <josejones <at> expedia.com>

Date: Mon, 10 Oct 2011 23:43:02 UTC

Severity: normal

Found in version 24.0.50

Done: Chong Yidong <cyd <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: josejones <at> expedia.com, 9723 <at> debbugs.gnu.org
Subject: Re: bug#9723: 24.0.50; Emacs Clipboard crash
Date: Fri, 21 Oct 2011 11:14:17 +0200
> From: Andreas Schwab <schwab <at> linux-m68k.org>
> Cc: Joseph Jones <josejones <at> expedia.com>,  9723 <at> debbugs.gnu.org
> Date: Fri, 21 Oct 2011 11:04:15 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> #12 0x01002eb0 in shut_down_emacs (sig=1, no_x=11551144, stuff=11546872) at emacs.c:2039
> >> #13 0x010010b6 in __mingw_CRTStartup ()
> >> #14 0x01001148 in WinMainCRTStartup ()
> >> #15 0x00000001 in ?? ()
> >> #16 0x00000001 in ?? ()
> >> #17 0x00000000 in ?? ()
> >
> > I don't understand this backtrace.  It says that Emacs was being shut
> > down because of a fatal signal.  sig=1 on Windows means SIGHUP, and
> > the only relevant place seems to be this line in keyboard.c:
> 
> That looks more like main, with argc == 1 and argv, envp following.  The
> second argument of shut_down_emacs is a boolean.

You are probably right.  Any idea how the backtrace could be mangled
like that, though?  Bad debug info?




This bug report was last modified 13 years and 8 days ago.

Previous Next


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