From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 2956@emacsbugs.donarmstrong.com, erikcharlebois@gmail.com
Subject: bug#2956: 23.0.92; anything.el causes BSOD on vista64 dual-processor
Date: Sat, 11 Apr 2009 16:39:00 +0200 [thread overview]
Message-ID: <m263hbtfuj.fsf@igel.home> (raw)
In-Reply-To: <83fxgfmgry.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 11 Apr 2009 17:00:49 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> 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?
An unprivileged process able to crash the OS is always a bug in the OS.
This is independent of whether there is a workaround.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-04-11 14:39 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
2009-04-11 14:39 ` Andreas Schwab [this message]
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=m263hbtfuj.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=2956@emacsbugs.donarmstrong.com \
--cc=eliz@gnu.org \
--cc=erikcharlebois@gmail.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.