GNU bug report logs - #17411
24.4.50; emacs_backtrace.txt

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: lekktu <at> gmail.com, 17340 <at> debbugs.gnu.org, monnier <at> IRO.UMontreal.CA, 17411 <at> debbugs.gnu.org
Subject: bug#17411: 24.4.50; emacs_backtrace.txt
Date: Sat, 26 Dec 2015 16:24:05 +0200

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: Stefan Monnier <monnier <at> IRO.UMontreal.CA>,  17340 <at> debbugs.gnu.org,  lekktu <at> gmail.com,  17411 <at> debbugs.gnu.org
> Date: Sat, 26 Dec 2015 15:16:56 +0100
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> From: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
> >> Cc: lekktu <at> gmail.com, 17411 <at> debbugs.gnu.org
> >> Date: Tue, 13 May 2014 17:19:50 -0400
> >> 
> >> I'd "fprintf (stderr, ...)", but that wouldn't work under w32 would
> >> it?
> >
> > Not if Emacs was invoked by clicking the desktop icon, which is the
> > usual way, no.
> >
> > Perhaps we should add a feature to write arbitrary text into the
> > emacs_backtrace.txt file, when Emacs crashes.
> 
> It's unclear what the conclusion was in this report -- whether there was
> something more to investigate or not...

I think it should be closed.  These problems didn't happen in a long
while.

Previous Next

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