Description of problem: It happened while I was working with podman containers and scripts, maybe happened because I ctrl-c'ed the SSH connection very quickly Version-Release number of selected component: waypipe-0.8.6-4.fc39 Additional info: reporter: libreport-2.17.11 type: CCpp reason: waypipe killed by SIGABRT journald_cursor: s=a22eb5d38c2c4b07808f41fa80e873f7;i=481ee1d;b=83473e9ca3aa4d719fbdc4b1cdc39d81;m=10c03216e9;t=6106c19f4f093;x=46c3bb357e4554a0 executable: /usr/bin/waypipe cmdline: waypipe -n ssh -A -p 39937 -o $'SendEnv GH_TOKEN' coder@localhost cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-95a3a73f-2fc2-4792-8801-056204dab264.scope rootdir: / uid: 1000 kernel: 6.6.13-200.fc39.x86_64 package: waypipe-0.8.6-4.fc39 runlevel: N 5 backtrace_rating: 4 crash_function: handle_sigint comment: It happened while I was working with podman containers and scripts, maybe happened because I ctrl-c'ed the SSH connection very quickly Truncated backtrace: Thread no. 1 (1 frames) #4 handle_sigint at ../src/util.c:129
Created attachment 2014679 [details] File: proc_pid_status
Created attachment 2014680 [details] File: maps
Created attachment 2014681 [details] File: limits
Created attachment 2014682 [details] File: open_fds
Created attachment 2014683 [details] File: mountinfo
Created attachment 2014684 [details] File: os_info
Created attachment 2014685 [details] File: cpuinfo
Created attachment 2014686 [details] File: core_backtrace
Created attachment 2014687 [details] File: dso_list
Created attachment 2014688 [details] File: backtrace
Created attachment 2014689 [details] File: environ
> maybe happened because I ctrl-c'ed the SSH connection very quickly Indeed that "#4 handle_sigint at ../src/util.c:129" is an abort() if ^C comes in after a previous ^C was handled -- there should have been a "second interrupt, aborting" message as well. I don't see the usefulnes of calling abort there, I've asked upstream if it'd make sense to change to something else here: https://gitlab.freedesktop.org/mstoeckl/waypipe/-/issues/96 It'll probably get "fixed" in the next version but until then it's not really a bug so closing this as there's not much else I can do (you can still reply if you want); thanks for the report!
That is very quick reaction time! (I've got a recurring crash that has a fix upstream since a few weeks and that doesn't get the update, but here is not the place to discuss it). Thanks for the explanation, the behavior can make sense.
> (I've got a recurring crash that has a fix upstream since a few weeks and that doesn't get the update, but here is not the place to discuss it). If this is a real annoyance you can point me at the issue/commit and I'll either ask for a new release and/or pick the patch up, but you're right another bz would probably be better to track this :)