From: John Wiegley <jwiegley@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 22252@debbugs.gnu.org
Subject: bug#22252: 24.5; emacs_backtrace.txt
Date: Wed, 30 Dec 2015 11:20:44 -0800 [thread overview]
Message-ID: <m2k2nvlp4j.fsf@newartisans.com> (raw)
In-Reply-To: <c8dfd1a3-fd84-4ea0-a42b-31359966ad47@default> (Drew Adams's message of "Wed, 30 Dec 2015 08:46:55 -0800 (PST)")
>>>>> Drew Adams <drew.adams@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
prev parent reply other threads:[~2015-12-30 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 23:45 bug#22252: 24.5; emacs_backtrace.txt Drew Adams
2015-12-30 4:53 ` John Wiegley
2015-12-30 16:46 ` Drew Adams
2015-12-30 19:20 ` John Wiegley [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2k2nvlp4j.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=22252@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.