bug#14205: 24.3.50; emacs_backtrace.txt

bug#14205: 24.3.50; emacs_backtrace.txt

[Drew Adams]

Backtrace:
0x01159601
0x01159673
0x01001459
0x01021A5E
0x0114F38D
0x7E418730
0x7E418812
0x7E4189C9
0x7E418A0C
0x0114DC15
0x0114DEB4
0x7C80B725 

In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
 of 2013-04-09 on ODIEONE
Bzr revision: 112253 rgm@gnu.org-20130409101736-f1vzgrwt88suqqis
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'
 

bug#14205: 24.3.50; emacs_backtrace.txt

[Juanma Barranquero]

??
??:0
w32_backtrace at w32fns.c:7685
emacs_abort at w32fns.c:7717
terminate_due_to_signal at emacs.c:343
die at alloc.c:6522
w32_wnd_proc at w32fns.c:3133
??
??:0
??
??:0
??
??:0
??
??:0
w32_msg_pump at w32fns.c:2454
w32_msg_worker@4 at w32fns.c:2580
??
??:0

bug#14205: 24.3.50; emacs_backtrace.txt

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 15 Apr 2013 01:37:15 +0200
> Cc: 14205@debbugs.gnu.org
> 
> ??
> ??:0
> w32_backtrace at w32fns.c:7685
> emacs_abort at w32fns.c:7717
> terminate_due_to_signal at emacs.c:343
> die at alloc.c:6522
> w32_wnd_proc at w32fns.c:3133

The trap caught the beast!

This bug is a duplicate of #14062; I will reply there.

Thanks.

bug#14205: 24.3.50; emacs_backtrace.txt

[Drew Adams]

> > w32_backtrace at w32fns.c:7685
> > emacs_abort at w32fns.c:7717
> > terminate_due_to_signal at emacs.c:343
> > die at alloc.c:6522
> > w32_wnd_proc at w32fns.c:3133
> 
> The trap caught the beast!

Glad to see something good come from reporting such a backtrace.
Thanks for looking into it, both of you.

I've downloaded Juanma's new Windows binary.  Will let you know if I get another
crash with backtrace.

bug#14205: 24.3.50; emacs_backtrace.txt

[Juanma Barranquero]

On Mon, Apr 15, 2013 at 3:34 PM, Drew Adams <drew.adams@oracle.com> wrote:

> I've downloaded Juanma's new Windows binary.  Will let you know if I get another
> crash with backtrace.

If you get a new backtrace, please send it to bug#14062's thread.

bug#14205: 24.3.50; emacs_backtrace.txt

[Drew Adams]

> If you get a new backtrace, please send it to bug#14062's thread.

OK, I'll try to remember that.

But what if I get a backtrace that is from something different?  I won't know
the difference.

Wouldn't you prefer that I file a new bug, and then, if you determine that it is
the same thing, we merge it?  That's the usual procedure.

bug#14205: 24.3.50; emacs_backtrace.txt

[Juanma Barranquero]

On Mon, Apr 15, 2013 at 4:34 PM, Drew Adams <drew.adams@oracle.com> wrote:

> Wouldn't you prefer that I file a new bug, and then, if you determine that it is
> the same thing, we merge it?  That's the usual procedure.

A new bug report can be created afterwards, if needed.

bug#14205: 24.3.50; emacs_backtrace.txt

[Eli Zaretskii]

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: "'Eli Zaretskii'" <eliz@gnu.org>, <14205@debbugs.gnu.org>
> Date: Mon, 15 Apr 2013 07:34:37 -0700
> 
> > If you get a new backtrace, please send it to bug#14062's thread.
> 
> OK, I'll try to remember that.
> 
> But what if I get a backtrace that is from something different?  I won't know
> the difference.

If the backtrace is _very_ different, like much-much longer, then
report a new bug.  Otherwise, it is best to report to 14062.

Thanks.