| #
20941a42 |
| 28-Nov-2023 |
riastradh <riastradh@NetBSD.org> |
pthread: Don't adjust user-allocated stack addresses by guardsize.
PR lib/57721
XXX pullup-10
XXX pullup-9
XXX pullup-8
|
| #
a76ca770 |
| 28-Nov-2023 |
riastradh <riastradh@NetBSD.org> |
libpthread/t_stack: Fix format string for size_t.
Tested this on i386 since that had been crashing before, but i386
doesn't see %zu for unsigned int as a problem.
PR lib/57721
XXX pullup-10
XXX pu
libpthread/t_stack: Fix format string for size_t.
Tested this on i386 since that had been crashing before, but i386
doesn't see %zu for unsigned int as a problem.
PR lib/57721
XXX pullup-10
XXX pullup-9
XXX pullup-8
show more ...
|
| #
2852ab88 |
| 27-Nov-2023 |
riastradh <riastradh@NetBSD.org> |
libpthread/t_stack: Appease gcc12 maybe-uninitialized warning.
The jmp_buf is not, in fact, uninitialized at the point of use, but
it doesn't hurt to narrow the scope a bit to between when the jmp_b
libpthread/t_stack: Appease gcc12 maybe-uninitialized warning.
The jmp_buf is not, in fact, uninitialized at the point of use, but
it doesn't hurt to narrow the scope a bit to between when the jmp_buf
is initialized by setjmp, and when the signal handler might be called
after sigaction.
Noted by prlw1.
PR lib/57721
XXX pullup-10
XXX pullup-9
XXX pullup-8
show more ...
|
| #
1ce2050a |
| 27-Nov-2023 |
riastradh <riastradh@NetBSD.org> |
libpthread/t_stack: Omit needless cast in previous.
Arose from an earlier draft of the change.
PR lib/57721
XXX pullup-10
XXX pullup-9
XXX pullup-8
|
| #
73a871b2 |
| 27-Nov-2023 |
riastradh <riastradh@NetBSD.org> |
libpthread/t_stack: Make this more robust to the guard size bug.
Make sure to allocate enough space for the thread's stack for a guard
even though there shouldn't be one, so that when we run the thr
libpthread/t_stack: Make this more robust to the guard size bug.
Make sure to allocate enough space for the thread's stack for a guard
even though there shouldn't be one, so that when we run the thread,
it doesn't start with the stack pointer pointing into someone else's
allocation (like malloc) causing stack frames to trash another data
structure -- or causing the user of that data structure to trash the
stack frames.
PR lib/57721
XXX pullup-10
XXX pullup-9
XXX pullup-8
show more ...
|
| #
5b36b4ea |
| 24-Nov-2023 |
riastradh <riastradh@NetBSD.org> |
pthread: Add tests for pthread user stack allocation.
PR lib/57721
XXX pullup-10
XXX pullup-9
XXX pullup-8
|