rust/src/libstd/sys/windows/thread.rs, branch 1.26.0

Use a range to identify SIGSEGV in stack guards

2018-01-31T19:41:29+00:00

Previously, the `guard::init()` and `guard::current()` functions were returning a `usize` address representing the top of the stack guard, respectively for the main thread and for spawned threads. The `SIGSEGV` handler on `unix` targets checked if a fault was within one page below that address, if so reporting it as a stack overflow. Now `unix` targets report a `Range` representing the guard memory, so it can cover arbitrary guard sizes. Non-`unix` targets which always return `None` for guards now do so with `Option`, so they don't pay any overhead. For `linux-gnu` in particular, the previous guard upper-bound was `stackaddr + guardsize`, as the protected memory was *inside* the stack. This was a glibc bug, and starting from 2.27 they are moving the guard *past* the end of the stack. However, there's no simple way for us to know where the guard page actually lies, so now we declare it as the whole range of `stackaddr ± guardsize`, and any fault therein will be called a stack overflow. This fixes #47863.

std: Avoid use of `libc` in portable modules

2017-11-09T15:56:44+00:00

This commit removes usage of the `libc` crate in "portable" modules like those at the top level and `sys_common`. Instead common types like `*mut u8` or `u32` are used instead of `*mut c_void` or `c_int` as well as switching to platform-specific functions like `sys::strlen` instead of `libc::strlen`.

Merge branch 'master' into threadname

2017-09-14T13:19:53+00:00

Move default stack min size to thread implementations

2017-09-13T08:56:41+00:00

The default min stack size value is smaller on l4re and therefore this value has to be different depending on the platform.

Implement named threads on Windows

2017-09-06T19:40:34+00:00

std: Handle OS errors when joining threads

2017-08-27T02:36:46+00:00

Also add to the documentation that the `join` method can panic. cc #34971 cc #43539

Use `#[prelude_import]` in `libstd`.

2016-08-24T22:12:48+00:00

Fixup #32476

2016-03-26T08:12:05+00:00

Fix unsound behaviour with null characters in thread names (issue #32475)

2016-03-25T05:14:03+00:00

Previously, the thread name (&str) was converted to a CString in the new thread, but outside unwind::try, causing a panic to continue into FFI. This patch changes that behaviour, so that the panic instead happens in the parent thread (where panic infrastructure is properly set up), not the new thread. This could potentially be a breaking change for architectures who don't support thread names. Signed-off-by: David Henningsson

Fix warnings during tests

2016-01-26T17:29:28+00:00

The deny(warnings) attribute is now enabled for tests so we need to weed out these warnings as well.