diff options
author | Andrew Burgess <andrew.burgess@embecosm.com> | 2021-06-18 12:56:03 +0100 |
---|---|---|
committer | Andrew Burgess <andrew.burgess@embecosm.com> | 2021-08-11 12:35:14 +0100 |
commit | 270135645b50a2fb8a4dac216584e8056167ffcc (patch) | |
tree | 5204f7678acb55014cc5478e21a8b8e42ccfd0a7 /configure | |
parent | bbefac7df96061a56dc4f17ef548382bdf4c3166 (diff) | |
download | fsf-binutils-gdb-270135645b50a2fb8a4dac216584e8056167ffcc.zip fsf-binutils-gdb-270135645b50a2fb8a4dac216584e8056167ffcc.tar.gz fsf-binutils-gdb-270135645b50a2fb8a4dac216584e8056167ffcc.tar.bz2 |
gdb: rename async_init_signals to gdb_init_signals
The async_init_signals has, for some time, dealt with async and sync
signals, so removing the async prefix makes sense I think.
Additionally, as pointed out by Pedro:
.....
The comments relating to SIGTRAP and SIGQUIT within this function are
out of date.
The comments for SIGTRAP talk about the signal disposition (SIG_IGN)
being passed to the inferior, meaning the signal disposition being
inherited by GDB's fork children. However, we now call
restore_original_signals_state prior to forking, so the comment on
SIGTRAP is redundant.
The comments for SIGQUIT are similarly out of date, further, the
comment on SIGQUIT talks about problems with BSD4.3 and vfork,
however, we have not supported BSD4.3 for several years now.
Given the above, it seems that changing the disposition of SIGTRAP is
no longer needed, so I've deleted the signal() call for SIGTRAP.
Finally, the header comment on the function now called
gdb_init_signals was getting quite out of date, so I've updated it
to (hopefully) better reflect reality.
There should be no user visible change after this commit.
Diffstat (limited to 'configure')
0 files changed, 0 insertions, 0 deletions