From: "Drew Adams" <drew.adams@oracle.com>
To: 12908@debbugs.gnu.org
Subject: bug#12908: 24.3.50; file `emacs_backtrace.txt'?
Date: Fri, 16 Nov 2012 10:30:34 -0800 [thread overview]
Message-ID: <4B9EFDFEE27E43DBB6331605DD7C2842@us.oracle.com> (raw)
Still getting many crashes (every session), but now I notice that Emacs
is creating a file `emacs_backtrace.txt' in the current directory (or
perhaps it is in the dir in which Emacs was started?).
I looked in the Emacs manual, the Elisp manual, and NEWS for some
information about this file, but found nothing (so there is a doc bug,
at least).
What is the file for, how are users to use it and control whether and
where it is written, etc.?
Here is the content of one such file, in case it helps in some way
(which I doubt):
Backtrace:
0x0115470D
0x0115477F
0x01001459
0x01021A07
0x012072B8
0x012080B9
0x0103B54F
0x0104F14B
0x01038878
0x01010EDE
0x0103800B
0x0101093B
0x01037FC5
0x0103757F
0x010378AC
0x010029AB
0x010010F9
0x7C817073
Backtrace:
0x0115470D
0x0115477F
0x01001459
0x01021A07
0x01063E40
0x010030FF
0x01001411
0x01021A07
0x01208B6F
0x01206FA0
0x01203D74
0x0103B556
0x0104F14B
0x01038878
0x01010EDE
0x0103800B
0x0101093B
0x01037FC5
0x0103757F
0x010378AC
0x010029AB
0x010010F9
0x7C817073
Backtrace:
0x0115470D
0x0115477F
0x01001459
0x01144D4F
0x01144D2A
0x01144D83
0x010011E6
0x7C8438F6
Backtrace:
0x0115470D
0x0115477F
0x01001459
0x01144D4F
0x01144D2A
0x01144D83
0x010011E6
0x7C8438F6
Backtrace:
0x0115470D
0x0115477F
0x01001459
0x01021A07
0x01063E40
0x010030FF
0x01001411
0x01021A07
0x01271987
0x012753CF
0x01201334
0x01202410
0x0121160D
0x01208C14
0x01010FC6
0x01208BA1
0x01206FA0
0x01203D74
0x0103B556
0x0104F14B
0x01038878
0x01010EDE
0x0103800B
0x0101093B
0x01037FC5
0x0103757F
0x010378AC
0x010029AB
0x010010F9
0x7C817073
Backtrace:
0x0115470D
0x0115477F
0x01001459
0x01021A07
0x010EFEEA
0x010F6A68
0x010F5208
0x010F48F4
0x010F4616
0x0120710E
0x01203D74
0x0103B556
0x0104F14B
0x01038878
0x01010EDE
0x0103800B
0x0101093B
0x01037FC5
0x0103757F
0x010378AC
0x010029AB
0x010010F9
0x7C817073
Backtrace:
0x0115470D
0x0115477F
0x01001459
0x01144D4F
0x01144D2A
0x01144D83
0x010011E6
0x7C8438F6
Backtrace:
0x0115470D
0x0115477F
0x01001459
0x01021A07
0x012D32D3
0x01014F64
0x010E117F
0x01015E7E
0x01015317
0x010E117F
0x01015E7E
0x01015317
0x010E117F
0x01015E7E
0x01015317
0x010E117F
0x01015E7E
0x01015317
0x010E6C1C
0x01014FD5
0x01014733
0x01052C55
0x010390C7
0x01010EDE
0x0103800B
0x0101093B
0x01037FC5
0x0103757F
0x010378AC
0x010029AB
0x010010F9
0x7C817073
In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
of 2012-11-05 on MS-W7-DANI
Bzr revision: 110809 lekktu@gmail.com-20121105172930-a5gn0bwi4lndchhw
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --cflags
-I../../libs/libXpm-3.5.10/include -I../../libs/libXpm-3.5.10/src
-I../../libs/libpng-1.2.37-lib/include -I../../libs/zlib-1.2.5
-I../../libs/giflib-4.1.4-1-lib/include
-I../../libs/jpeg-6b-4-lib/include
-I../../libs/tiff-3.8.2-1-lib/include
-I../../libs/libxml2-2.7.8-w32-bin/include/libxml2
-I../../libs/gnutls-3.0.9-w32-bin/include
-I../../libs/libiconv-1.9.2-1-lib/include'
next reply other threads:[~2012-11-16 18:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 18:30 Drew Adams [this message]
2012-11-16 18:40 ` bug#12908: 24.3.50; file `emacs_backtrace.txt'? Juanma Barranquero
2012-11-16 19:08 ` Drew Adams
2012-11-16 19:42 ` Eli Zaretskii
2012-11-16 21:02 ` Drew Adams
2012-11-17 7:23 ` Eli Zaretskii
2012-11-17 16:36 ` Drew Adams
2012-11-16 21:49 ` Stefan Monnier
2012-11-17 7:27 ` Eli Zaretskii
2012-11-16 19:00 ` Eli Zaretskii
2012-11-16 19:22 ` Drew Adams
2012-11-16 19:39 ` Eli Zaretskii
2012-11-16 20:56 ` Drew Adams
2012-11-17 7:21 ` Eli Zaretskii
2012-11-17 16:36 ` Drew Adams
2012-11-17 18:45 ` Paul Eggert
2012-11-17 19:09 ` Eli Zaretskii
2012-11-17 19:29 ` Paul Eggert
2012-11-17 19:42 ` Eli Zaretskii
2012-11-17 21:25 ` Paul Eggert
2012-11-17 23:08 ` bug#12911: " Drew Adams
2012-11-18 1:12 ` Paul Eggert
2012-11-18 1:19 ` bug#12911: " Paul Eggert
2012-11-18 3:55 ` Eli Zaretskii
2012-11-18 3:56 ` Eli Zaretskii
2012-11-18 4:04 ` Eli Zaretskii
2012-11-18 5:19 ` Paul Eggert
2012-11-18 17:16 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written Eli Zaretskii
2012-11-18 19:18 ` Paul Eggert
2012-11-18 21:10 ` Eli Zaretskii
2012-11-19 1:44 ` Stefan Monnier
2012-11-19 3:50 ` Eli Zaretskii
2012-11-17 23:01 ` bug#12908: 24.3.50; file `emacs_backtrace.txt'? Drew Adams
2012-11-18 1:24 ` Paul Eggert
2012-11-18 3:58 ` Eli Zaretskii
2012-11-18 4:40 ` Drew Adams
2012-11-18 17:53 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written Eli Zaretskii
2012-11-18 18:42 ` Drew Adams
2012-11-18 5:19 ` bug#12908: 24.3.50; file `emacs_backtrace.txt'? Paul Eggert
2012-11-18 17:08 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written Eli Zaretskii
2012-11-18 7:08 ` bug#12908: 24.3.50; file `emacs_backtrace.txt'? Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B9EFDFEE27E43DBB6331605DD7C2842@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=12908@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).