diff options
author | Keith Seitz <keiths@redhat.com> | 2025-05-12 09:28:02 -0700 |
---|---|---|
committer | Keith Seitz <keiths@redhat.com> | 2025-05-12 09:28:02 -0700 |
commit | a19c78180e083196ac741ffde4bc94d529c6808c (patch) | |
tree | ecbf2759bedc8880a864e584bcae0e8e4245ce24 /gdb/python/py-utils.c | |
parent | f891d8e69d936cc3458c059871992d24fbb8c3d3 (diff) | |
download | binutils-a19c78180e083196ac741ffde4bc94d529c6808c.zip binutils-a19c78180e083196ac741ffde4bc94d529c6808c.tar.gz binutils-a19c78180e083196ac741ffde4bc94d529c6808c.tar.bz2 |
[PATCH] Add syscall tests when following/detaching from fork
breakpoints/13457 discusses issues with syscall catchpoints when
following forks, lamenting that there is no coverage for the
various permutations of `follow-fork-mode' and `detach-on-fork'.
This is an attempt to try and cover some of this ground. Unfortunately
the state of syscall support when detaching after the fork is
very, very inconsistent across various architectures. [I've tested
extensively Fedora/RHEL platforms.]
Right now, the only reliable platform to run tests on is x86_64/i?86
for the specific case where we do not detach from the fork. Consequently,
this patch limits testing to those architectures.
I have updated breakpoints/13457 with my findings on failures with the
detaching case.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=13457
Approved-By: Andrew Burgess <aburgess@redhat.com>
Diffstat (limited to 'gdb/python/py-utils.c')
0 files changed, 0 insertions, 0 deletions