From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: macross84@ozu.es, 6430@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#6430: Emacs WINDOWS truncates exit status of processes to 8 bits
Date: Wed, 15 Jun 2016 20:22:25 +0200 [thread overview]
Message-ID: <8760tajori.fsf@wanadoo.es> (raw)
In-Reply-To: <83r3bycor8.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 15 Jun 2016 21:04:27 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> When using --with-wide-int (or when running on Windows 64bits) we have
>> the full 32 bits, right?
>
> No. The 2 bits are reserved by Windows, not by Emacs integer's
> representation. To see that in action, interrupt a program with
> Ctrl-C and look at the exit status: you will see 0xC000013A; the
> 0xC0000000 bits are the reserved ones. (There are more values for
> other fatal exit reasons, but all of them set those 2 bits.)
I thought that the limitation you referred to was about how many bits
Emacs has for representing integers on 32 bit platforms. The upper 2
bits reserved by Windows is an integral part of the exit code. A process
can return any value on the 32 bit range.
next prev parent reply other threads:[~2016-06-15 18:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 17:20 bug#6430: Emacs WINDOWS truncates exit status of processes to 8 bits macross84
2016-06-14 2:48 ` Noam Postavsky
2016-06-14 13:07 ` Óscar Fuentes
2016-06-14 14:35 ` Eli Zaretskii
2016-06-14 21:48 ` Noam Postavsky
2016-06-15 2:39 ` Eli Zaretskii
2016-06-15 12:30 ` Óscar Fuentes
2016-06-15 15:02 ` Eli Zaretskii
2016-06-15 15:15 ` Óscar Fuentes
2016-06-15 15:40 ` Eli Zaretskii
2016-06-15 17:14 ` Óscar Fuentes
2016-06-15 17:32 ` Eli Zaretskii
2016-06-15 17:36 ` Óscar Fuentes
2016-06-15 18:04 ` Eli Zaretskii
2016-06-15 18:22 ` Óscar Fuentes [this message]
2016-06-15 18:50 ` Eli Zaretskii
2016-06-15 19:32 ` Óscar Fuentes
2016-06-16 2:35 ` Eli Zaretskii
2016-06-16 4:13 ` Óscar Fuentes
2016-06-16 15:07 ` Eli Zaretskii
2016-06-16 17:56 ` Óscar Fuentes
2016-06-16 19:05 ` Eli Zaretskii
2020-11-19 4:05 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760tajori.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=6430@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=macross84@ozu.es \
--cc=npostavs@users.sourceforge.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).