rust/src/libstd/sys/windows/process.rs, branch 1.34.2https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.34.22019-02-20T05:37:30+00:00Refactor Windows stdio and remove stdin double buffering2019-02-20T05:37:30+00:00Paul Dickerpitdicker@gmail.com2019-02-14T05:35:20+00:00urn:sha1:f411852add58637a3b8628a8f70146106bdc9719std: Render large exit codes as hex on Windows2019-01-10T15:52:33+00:00Alex Crichtonalex@alexcrichton.com2019-01-09T17:35:09+00:00urn:sha1:bbb5448de447eeef2eae09a6df93553a6d1ccac7
On Windows process exit codes are never signals but rather always 32-bit
integers. Most faults like segfaults and such end up having large
integers used to represent them, like STATUS_ACCESS_VIOLATION being
0xC0000005. Currently, however, when an `ExitStatus` is printed this
ends up getting rendered as 3221225477 which is somewhat more difficult
to debug.
This commit adds a branch in `Display for ExitStatus` on Windows which
handles exit statuses where the high bit is set and prints those exit
statuses as hex instead of with decimals. This will hopefully preserve
the current display for small exit statuses (like `exit code: 22`), but
assist in quickly debugging segfaults/access violations/etc. I've
found at least that the hex codes are easier to search for than decimal.
I wasn't able to find any official documentation saying that all system
exit codes have the high bit set, but I figure it's a good enough
heuristic for now.
Remove licenses2018-12-26T04:08:33+00:00Mark Rousskovmark.simulacrum@gmail.com2018-12-25T15:56:47+00:00urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718cReplace usages of `..i + 1` ranges with `..=i`.2018-12-04T20:05:19+00:00Corey Farwellcoreyf@rwell.org2018-12-04T19:17:58+00:00urn:sha1:c025d6140999e07ddf0294f0676c64ff2322a210refactor: use shorthand fields2018-11-06T20:05:44+00:00teresyhi.teresy@gmail.com2018-11-06T20:05:44+00:00urn:sha1:eca11b99a7d25e4e6573472a16537c1aacb5d5e1Replace push loops with collect() and extend() where possible2018-07-29T16:53:22+00:00ljedrzljedrz@gmail.com2018-07-26T15:11:10+00:00urn:sha1:59c8a279daf6912b99ba089ff6dafbfc3469831eImport the `alloc` crate as `alloc_crate` in std2018-04-12T20:52:47+00:00Simon Sapinsimon.sapin@exyr.org2018-04-03T12:36:57+00:00urn:sha1:1b895d8b88413f72230fbc0f00c67328870a2e9a
… to make the name `alloc` available.
std: Inline some Termination-related methods2018-04-05T18:07:19+00:00Alex Crichtonalex@alexcrichton.com2018-04-05T18:07:19+00:00urn:sha1:323f8087910b0d63815003970bb8a45e3ccfdb17
These were showing up in tests and in binaries but are trivially optimize-able
away, so add `#[inline]` attributes so LLVM has an opportunity to optimize them
out.
Deprecate the AsciiExt trait in favor of inherent methods2018-03-21T16:54:33+00:00Simon Sapinsimon.sapin@exyr.org2018-03-17T11:15:24+00:00urn:sha1:c09b9f937250db0f51b705a3110f8cffdad083bb
The trait and some of its methods are stable and will remain.
Some of the newer methods are unstable and can be removed later.
Fixes https://github.com/rust-lang/rust/issues/39658
Move process::ExitCode internals to sys2018-03-04T02:44:44+00:00Scott McMurrayscottmcm@users.noreply.github.com2018-03-04T02:29:30+00:00urn:sha1:74c5c6e6cb0425284f57fece6fbf248e827ea06d
Now begins the saga of fixing compilation errors on other platforms...