Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion bug#12579: Emacs 24.1 / 24.2 daily crashes

Received: by 10.66.76.38 with SMTP id h6mr2746595paw.15.1349527970841;
        Sat, 06 Oct 2012 05:52:50 -0700 (PDT)
MIME-Version: 1.0
Path: g9ni28818pbh.1!nntp.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed.news.ucla.edu!usenet.stanford.edu!not-for-mail
From: Eli Zaretskii <e...@gnu.org>
Newsgroups: gnu.emacs.bug
Subject: bug#12579: Emacs 24.1 / 24.2 daily crashes
Date: Sat, 06 Oct 2012 14:51:56 +0200
Lines: 56
Sender: debbugs-submit-boun...@debbugs.gnu.org
Approved: bug-gnu-em...@gnu.org
Message-ID: <mailman.10434.1349527970.855.bug-gnu-emacs@gnu.org>
References: <80fw5rsuxp.fsf@somewhere.org>
Reply-To: Eli Zaretskii <e...@gnu.org>
NNTP-Posting-Host: lists.gnu.org
X-Trace: usenet.stanford.edu 1349527970 27796 208.118.235.17 (6 Oct 2012 12:52:50 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: 12...@debbugs.gnu.org
To: Fabrice Niessen <f...@missioncriticalit.com>
Envelope-to: bug-gnu-em...@gnu.org
X-Loop: help-debb...@gnu.org
Resent-From: Eli Zaretskii <e...@gnu.org>
Original-Sender: debbugs-submit-boun...@debbugs.gnu.org
Resent-CC: bug-gnu-em...@gnu.org
Resent-Date: Sat, 06 Oct 2012 12:53:01 +0000
Resent-Message-ID: <handler.12579.B12579.134952795411...@debbugs.gnu.org>
Resent-Sender: help-debb...@gnu.org
X-GNU-PR-Message: followup 12579
X-GNU-PR-Package: emacs,w32
X-GNU-PR-Keywords: moreinfo
In-reply-to: <80fw5rsuxp.fsf@somewhere.org>
X-012-Sender: ha...@inter.net.il
X-BeenThere: debbugs-sub...@debbugs.gnu.org
X-Mailman-Version: 2.1.13
Precedence: list
Errors-To: debbugs-submit-boun...@debbugs.gnu.org
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2)
X-Received-From: 140.186.70.43
X-BeenThere: bug-gnu-em...@gnu.org
List-Id: "Bug reports for GNU Emacs,
	the Swiss army knife of text editors" <bug-gnu-emacs.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-gnu-emacs>,
	<mailto:bug-gnu-emacs-requ...@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-gnu-emacs>
List-Post: <mailto:bug-gnu-em...@gnu.org>
List-Help: <mailto:bug-gnu-emacs-requ...@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-gnu-emacs>,
	<mailto:bug-gnu-emacs-requ...@gnu.org?subject=subscribe>
Bytes: 4835

> From: "Fabrice Niessen" <f...@missioncriticalit.com>
> Cc: 12...@debbugs.gnu.org
> Date: Sat, 06 Oct 2012 13:26:26 +0200
> 
> Attaching to process 5928
> [New Thread 5928.0x1904]
> [New Thread 5928.0x1c7c]
> [New Thread 5928.0x1644]
> [New Thread 5928.0x28c]
> Reading symbols from /cygdrive/c/Program Files/Emacs-24.2/bin/emacs.exe...done.
> warning: File "/cygdrive/c/Program Files/Emacs-24.2/.gdbinit" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
> (gdb) thread apply all backtrace

Since this _is_ a crash, you _must_ type "continue", wait for another
GDB prompt, and only then type "thread apply all backtrace".
Otherwise, you get a backtrace that is not useful.  Like this one:

> Thread 4 (Thread 5928.0x28c):
> #0  0x7c91120f in ntdll!DbgUiConnectToDbg () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> #1  0x7c962119 in ntdll!KiIntSystemCall () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> #2  0x00000005 in ?? ()
> #3  0x00000004 in ?? ()
> #4  0x00000001 in ?? ()
> #5  0x7132ffd0 in ?? ()
> #6  0x00000000 in ?? ()
> 
> Thread 3 (Thread 5928.0x1644):
> #0  0x7c91e514 in ntdll!LdrAccessResource () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> #1  0x7c91df5a in ntdll!ZwWaitForSingleObject () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> #2  0x7c8025db in WaitForSingleObjectEx () from /cygdrive/c/WINDOWS/system32/kernel32.dll
> #3  0x00000658 in ?? ()
> #4  0x00000000 in ?? ()
> 
> Thread 2 (Thread 5928.0x1c7c):
> #0  0x7c91e514 in ntdll!LdrAccessResource () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> #1  0x7e3991be in USER32!GetProcessWindowStation () from /cygdrive/c/WINDOWS/system32/USER32.dll
> #2  0x7e3991f1 in USER32!GetMessageW () from /cygdrive/c/WINDOWS/system32/USER32.dll
> #3  0x011490bd in w32_msg_pump (msg_buf=0x7236ff54) at w32fns.c:2263
> #4  0x011492fb in w32_msg_worker@4 (arg=0x0) at w32fns.c:2485
> #5  0x7c80b729 in KERNEL32!GetModuleFileNameA () from /cygdrive/c/WINDOWS/system32/kernel32.dll
> #6  0x00000000 in ?? ()
> 
> Thread 1 (Thread 5928.0x1904):
> #0  0x7c91e514 in ntdll!LdrAccessResource () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> #1  0x7c91df4a in ntdll!ZwWaitForMultipleObjects () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> #2  0x7c8648a2 in UnhandledExceptionFilter () from /cygdrive/c/WINDOWS/system32/kernel32.dll
> #3  0x00000002 in ?? ()
> #4  0x007b7f4c in ?? ()
> #5  0x7c8438fa in ValidateLocale () from /cygdrive/c/WINDOWS/system32/kernel32.dll
> #6  0x00000000 in ?? ()

Thread 1 is the interesting thread, but this backtrace just shows that
it is in an exception handler, which is not useful.