History log of /src/tests/lib/libc/sys/t_ptrace_core_wait.h |
Revision | | Date | Author | Comments |
1.10 |
| 02-May-2025 |
riastradh | tests/lib/libc/sys/t_ptrace*: Nix trailing whitespace.
No functional change intended.
Preparation for:
PR misc/59381: t_ptrace_wait* and t_ptrace_sigchld tests are flaky
|
1.9 |
| 29-Jun-2024 |
rin | core_dump_procinfo: Fix false positive for vax
Increment PC after trapped by `bpt`, as done for many other platforms.
|
1.8 |
| 24-Aug-2023 |
rin | t_ptrace_core_wait.h: Increment PC after trap, also for riscv
Fix *:core_dump_procinfo tests for riscv64.
|
1.7 |
| 09-Jun-2022 |
skrll | There are two hard problems in computer science cache invalidation, naming and off-by-one errors.
Fix a naming and off-by-one bug... Thanks to Tom Lane for spotting my typo.
|
1.6 |
| 07-Jun-2022 |
skrll | PR/56865: hppa: t_ptrace_core_wait test doesn't know it must advance PC after breakpoint
Add __hppa__ to the list of architectures that need to advance to the instruction after the breakpoint
Thanks to Tom Lane for the fix.
|
1.5 |
| 26-Mar-2022 |
martin | Add sparc* to the list of architectures that need an explicit address with PT_CONTINUE in this test.
|
1.4 |
| 24-Jul-2021 |
rin | For sh3, increment PC when PT_CONTINUE from trigger_trap(), as already done for aarch64, arm, and powerpc. Otherwise, child is trapped to the PTRACE_BREAKPOINT_ASM (== trapa) instruction indefinitely.
Fix tests/lib/libc/sys/t_ptrace_wait*:core_dump_procinfo.
|
1.3 |
| 15-Oct-2020 |
rin | Apply fix in rev 1.2 for core_dump_procinfo to aarch64 and arm:
http://cvsweb.netbsd.org/bsdweb.cgi/src/tests/lib/libc/sys/t_ptrace_core_wait.h#rev1.2
> For powerpc, program counter is not automatically incremented by trap > instruction. We cannot increment PC in the trap handler, which breaks > applications depending on this behavior, e.g., GDB.
This statement is true for aarch64 and arm.
Also, use PTRACE_BREAKPOINT_SIZE instead of hard-coded 4 to address instruction next to PC.
OK ryo
|
1.2 |
| 24-Jun-2020 |
rin | Fix core_dump_procinfo tests for powerpc, for which child process was stalled indefinitely in trap instruction even after PT_CONTINUE.
For powerpc, program counter is not automatically incremented by trap instruction. We cannot increment PC in the trap handler, which breaks applications depending on this behavior, e.g., GDB.
Therefore, we need to pass (PC + 4) instead of (void *)1 (== PC) to PT_CONTINUE when child process traps itself.
|
1.1 |
| 05-May-2020 |
kamil | Move core tests out of t_ptrace_wait.c to t_ptrace_core_wait.h
The same tests are now included with the preprocessor in t_ptrace_wait.c.
No functional change intended.
|