--- Begin Message ---
Subject: |
24.3.50; emacs_backtrace.txt |
Date: |
Thu, 31 Jan 2013 06:35:08 -0800 |
Backtrace:
0x01157A5C
0x01157ACE
0x01001459
0x01021E25
0x010169F2
0x010662D5
0x0100310C
0x01001411
0x01021E25
0x0114D589
0x7E418730
0x7E418812
0x7E4189C9
0x7E418A0C
0x0114BBA6
0x0114BE45
0x7C80B725
In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
of 2013-01-25 on ODIEONE
Bzr revision: 111604 address@hidden
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --cflags
-IC:/Devel/emacs/build/include --ldflags -LC:/Devel/emacs/build/lib'
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#13596: 24.3.50; emacs_backtrace.txt |
Date: |
Fri, 22 Feb 2013 20:03:44 -0500 |
User-agent: |
Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) |
Eli Zaretskii wrote:
> Without a recipe, I don't see what else can be done with this.
(Doesn't this apply to all these "here's a backtrace" reports?)
Hence closing.
I would suggest running unoptimized builds under GDB if crashes are
frequent, and keeping the sessions live for debugging.
--- End Message ---