GNU bug report logs - #22252
24.5; emacs_backtrace.txt

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22252 in the body.
You can then email your comments to 22252 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.5; emacs_backtrace.txt
Date: Sun, 27 Dec 2015 15:45:35 -0800 (PST)

Exception 0xc0000005 at this address:
010e6467

Backtrace:
01151828


In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/usr --host=i686-pc-mingw32'

Message #8 received at 22252 <at> debbugs.gnu.org (full text, mbox):

From: John Wiegley <jwiegley <at> gmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 22252 <at> debbugs.gnu.org
Subject: Re: bug#22252: 24.5; emacs_backtrace.txt
Date: Tue, 29 Dec 2015 20:53:20 -0800

>>>>> Drew Adams <drew.adams <at> oracle.com> writes:

> Exception 0xc0000005 at this address:
> 010e6467

> Backtrace:
> 01151828

> In GNU Emacs 24.5.1 (i686-pc-mingw32)
>  of 2015-04-11 on LEG570
> Windowing system distributor `Microsoft Corp.', version 6.1.7601
> Configured using:
>  `configure --prefix=/c/usr --host=i686-pc-mingw32'

Hi Drew,

With only this information as the bug report, I'm not sure what we can do?  Am
I missing something?

Typical questions:

  - What were you doing at the time this happened?
  - What did you expect to see?
  - Does it reproduce under any conditions?

Thanks,
-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

Message #11 received at 22252 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: John Wiegley <jwiegley <at> gmail.com>
Cc: 22252 <at> debbugs.gnu.org
Subject: RE: bug#22252: 24.5; emacs_backtrace.txt
Date: Wed, 30 Dec 2015 08:46:55 -0800 (PST)

> > Exception 0xc0000005 at this address:
> > 010e6467
> 
> > Backtrace:
> > 01151828
> 
> > In GNU Emacs 24.5.1 (i686-pc-mingw32)
> >  of 2015-04-11 on LEG570
> > Windowing system distributor `Microsoft Corp.', version 6.1.7601
> > Configured using:
> >  `configure --prefix=/c/usr --host=i686-pc-mingw32'
> 
> Hi Drew,
> 
> With only this information as the bug report, I'm not sure what we can do?
> Am I missing something?
> 
> Typical questions:
> 
>   - What were you doing at the time this happened?
>   - What did you expect to see?
>   - Does it reproduce under any conditions?

Answers:
 Nothing special, IIRC.  I don't recall exactly.
 Nothing special (I don't expect Emacs to crash, though ;-))
 I don't have a recipe to reproduce it.
Sorry.

Note that this is a crash from a release (24.5), not from a
development snapshot.

Message #14 received at 22252 <at> debbugs.gnu.org (full text, mbox):

From: John Wiegley <jwiegley <at> gmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 22252 <at> debbugs.gnu.org
Subject: Re: bug#22252: 24.5; emacs_backtrace.txt
Date: Wed, 30 Dec 2015 11:20:44 -0800

>>>>> Drew Adams <drew.adams <at> oracle.com> writes:

>> > Exception 0xc0000005 at this address:
>> > 010e6467
>> 
>> > Backtrace:
>> > 01151828
>> 
>> > In GNU Emacs 24.5.1 (i686-pc-mingw32)
>> >  of 2015-04-11 on LEG570
>> > Windowing system distributor `Microsoft Corp.', version 6.1.7601
>> > Configured using:
>> >  `configure --prefix=/c/usr --host=i686-pc-mingw32'
>> 
>> Hi Drew,
>> 
>> With only this information as the bug report, I'm not sure what we can do?
>> Am I missing something?
>> 
>> Typical questions:
>> 
>> - What were you doing at the time this happened?
>> - What did you expect to see?
>> - Does it reproduce under any conditions?

> Answers:
>  Nothing special, IIRC.  I don't recall exactly.
>  Nothing special (I don't expect Emacs to crash, though ;-))
>  I don't have a recipe to reproduce it.
> Sorry.

> Note that this is a crash from a release (24.5), not from a
> development snapshot.

OK, and I appreciate the conscientiousness, but without any means of
reproduction, and no way of knowing what could have caused the crash, I have
to close this report as unreproducible.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

Previous Next

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