newly discovered computer issue: on system76 laptops, only when using the internal keyboard, pressing Ctrl+C kills the `glasgow repl` interpreter, instead of clearing the command buffer like usual
with a USB keyboard it works fine
newly discovered computer issue: on system76 laptops, only when using the internal keyboard, pressing Ctrl+C kills the `glasgow repl` interpreter, instead of clearing the command buffer like usual
with a USB keyboard it works fine
it's probably a race condition of some sort with the python async exception raising mechanism because the backtrace points here, even if you only hit ^C once
maybe combined with a debouncing issue with the keyboard?
obviously it doesn't crash under strace, even if you invoke it as `strace -e '!all' --signal=sigint python ...` to limit the degree to which it serializes execution
@whitequark Is this running on the laptop, or on device sending input from laptop? Seems like something would have to be very wrong with how ^C is handled for this to happen...
@whitequark maybe use tracing events to see how many SIGINTs are sent?
echo 1 | sudo tee /sys/kernel/tracing/events/signal/signal_generate/enable
sudo cat /sys/kernel/debug/tracing/trace_pipe
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.