Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
uname output: Linux ########.fraunhofer.de 5.15.12-200.fc35.x86_64
#1 SMP Wed Dec 29 15:03:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-redhat-linux-gnu
Bash Version: 5.1
Patch Level: 8
Release Status: release
Description:
The position of the cursor changes to the first column when bash,
running inside xterm, receives the signal SIGALRM
Expected behavior: No change in cursor position
Repeat-By:
# Start a bash in xterm w/o customizations
xterm -class nothing -e bash --norc &
# within this xterm, enter:
function sigalarm_test { echo -n ; } # define an empty signal handler
trap sigalarm_test SIGALRM # install the signal handler
echo $$ # report the shells PID
# in a different shell, send SIGALRM to the PID of the previously
started bash
kill -s SIGALRM PID # use the PID reported by 'echo
$$' above
=> now the cursor position jumps to the first column in the xterm
running bash
So far I've watched this behavior only with SIGALRM.
