| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cross-platform-actions/action](https://github.com/cross-platform-actions/action) from 0.26.0 to 0.27.0.
- [Release notes](https://github.com/cross-platform-actions/action/releases)
- [Changelog](https://github.com/cross-platform-actions/action/blob/master/changelog.md)
- [Commits](https://github.com/cross-platform-actions/action/compare/v0.26.0...v0.27.0)
---
updated-dependencies:
- dependency-name: cross-platform-actions/action
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
|
|
|
| |
Link: https://github.com/actions/runner-images/issues/9524#issuecomment-2002065399
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Valgrind does not deliver async signals in a timely manner; by default,
it polls for new signals every 1,000 basic blocks. That means we can
get SIGALRM delivered after timer_delete(), or kill(SIGSEGV) never
delivered after pause().
Fix the timer_delete() issue by reordering the cleanup path. Valgrind
always polls pending signals after pthread_sigmask(), so call that
between timer_delete() and sigunhook().
Fix the pause() issue by sleeping in a loop instead.
Note that --fair-sched=yes is required to avoid starvation of the
background thread.
Link: https://bugs.kde.org/show_bug.cgi?id=492678
Link: https://bugs.kde.org/show_bug.cgi?id=343357
Link: https://bugs.kde.org/show_bug.cgi?id=498936
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Otherwise the child process runs with all signals blocked.
Fixes: 423cfa4 ("xspawn: Mask signals before fork()")
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This lets us use them on GCC >= 13, even before C23.
|
| |
|
| |
|
| |
|
|
|
|
| |
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=66dd34ad31e5963d72a700ec3f2449291d322921
|
|
|
|
|
|
|
|
|
|
| |
macOS always fills in si_code for SIG{BUS,ILL,SEGV} as if it were a real
hardware fault, so returning from the handler is not guaranteed to re-
trigger the signal.
Fixes: aecdabb ("sighook: Return instead of re-raising for faults")
Link: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2386463/4/util/posix/signals_test.cc
Link: https://github.com/chromium/crashpad/commit/e0d8a0aa01ac176804077f1f128ccc894c098f79
|
| |
|
|
|
|
| |
Link: https://savannah.gnu.org/bugs/index.php?45930
|
| |
|
|
|
|
|
| |
This wraps __sanitizer_annotate_contiguous_container() to give
byte-precise tracking of usable allocation sizes with ASan.
|
|
|
|
|
| |
It's probably nicer to avoid evaluating expensive arguments when not
sanitizing, rather than relying on the optimizer to clean them up.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cross-platform-actions/action](https://github.com/cross-platform-actions/action) from 0.25.0 to 0.26.0.
- [Release notes](https://github.com/cross-platform-actions/action/releases)
- [Changelog](https://github.com/cross-platform-actions/action/blob/master/changelog.md)
- [Commits](https://github.com/cross-platform-actions/action/compare/v0.25.0...v0.26.0)
---
updated-dependencies:
- dependency-name: cross-platform-actions/action
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The new ioq_submit() function is now necessary to call to ensure the
pending request batch is flushed.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This helps avoid situations where multiple waiters block on different
slots using the same monitor, which happened more often than expected
due to correlations caused by batching.
|
|
|
|
|
| |
Also, cache-align struct ioq_ent to avoid false sharing when two workers
are handling neighbouring requests.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the death look exactly like it would if we didn't handle the
signal at all. Coredumps will point at the right instruction, segfaults
will get logged in dmesg again, etc.
Technically POSIX says this is undefined, but if we get a fault, we've
already done something undefined anyway ;)
Link: https://github.com/rust-lang/rust/issues/26458
|
|
|
|
| |
QNX doesn't support SA_RESTART.
|
| |
|