From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
2956@emacsbugs.donarmstrong.com
Cc: erikcharlebois@gmail.com
Subject: bug#2956: 23.0.92; anything.el causes BSOD on vista64 dual-processor
Date: Sat, 11 Apr 2009 17:00:49 +0300 [thread overview]
Message-ID: <83fxgfmgry.fsf@gnu.org> (raw)
In-Reply-To: <jwvfxgf1hce.fsf-monnier+emacsbugreports@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sat, 11 Apr 2009 08:55:32 -0400
> Cc: 2956@emacsbugs.donarmstrong.com
>
> > Running "M-x anything" with anything.el, then pressing tab and enter
> > causes Vista 64 to BSOD with a "Second processor failed to respond to
> > clock interrupt in time" error. I am running on a dual quad-core system.
>
> That's clearly a bug in Vista rather than in Emacs, so there's nothing
> for us to fix.
The fact (if it is a fact) that a problem manifests itself only on
Vista does not necessarily mean there's no bug in Emacs, especially
since the variety of different systems on which Emacs is routinely
tested is so small. Some positive evidence is required to deduce that
the bug is in the underlying OS. Do you have such an evidence?
next prev parent reply other threads:[~2009-04-11 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvprfjyrlk.fsf-monnier+emacsbugreports@gnu.org>
2009-04-11 0:09 ` bug#2956: 23.0.92; anything.el causes BSOD on vista64 dual-processor Erik Charlebois
2009-04-11 12:55 ` Stefan Monnier
2009-04-11 14:00 ` Eli Zaretskii [this message]
2009-04-11 14:39 ` Andreas Schwab
2009-04-11 15:49 ` Eli Zaretskii
2009-04-11 16:28 ` Andreas Schwab
2009-04-11 16:58 ` Lennart Borgman
2009-04-11 18:11 ` Eli Zaretskii
2009-04-11 18:40 ` bug#2956: marked as done (23.0.92; anything.el causes BSOD on vista64 dual-processor) Emacs bug Tracking System
2009-04-11 19:09 ` bug#2956: 23.0.92; anything.el causes BSOD on vista64 dual-processor Eli Zaretskii
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=83fxgfmgry.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=2956@emacsbugs.donarmstrong.com \
--cc=erikcharlebois@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.