Bug 2262447

Summary: [abrt] waypipe: handle_sigint(): waypipe killed by SIGABRT
Product: [Fedora] Fedora Reporter: Albert Larsan <albertlarsan>
Component: waypipeAssignee: Dominique Martinet <g.fhnrunznrqeqf>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: albertlarsan, g.fhnrunznrqeqf, ofourdan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9a29aaefa77b73658ec377572917a10e60c6ee5
Whiteboard: abrt_hash:a16a1b1132839bf5f58426e1d891906db0e7df08;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-02-02 21:02:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: backtrace
none
File: environ none

Description Albert Larsan 2024-02-02 20:43:35 UTC 
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
Comment 1 Albert Larsan 2024-02-02 20:43:39 UTC 
Created attachment 2014679 [details]
File: proc_pid_status
Comment 2 Albert Larsan 2024-02-02 20:43:41 UTC 
Created attachment 2014680 [details]
File: maps
Comment 3 Albert Larsan 2024-02-02 20:43:42 UTC 
Created attachment 2014681 [details]
File: limits
Comment 4 Albert Larsan 2024-02-02 20:43:44 UTC 
Created attachment 2014682 [details]
File: open_fds
Comment 5 Albert Larsan 2024-02-02 20:43:46 UTC 
Created attachment 2014683 [details]
File: mountinfo
Comment 6 Albert Larsan 2024-02-02 20:43:47 UTC 
Created attachment 2014684 [details]
File: os_info
Comment 7 Albert Larsan 2024-02-02 20:43:48 UTC 
Created attachment 2014685 [details]
File: cpuinfo
Comment 8 Albert Larsan 2024-02-02 20:43:50 UTC 
Created attachment 2014686 [details]
File: core_backtrace
Comment 9 Albert Larsan 2024-02-02 20:43:51 UTC 
Created attachment 2014687 [details]
File: dso_list
Comment 10 Albert Larsan 2024-02-02 20:43:53 UTC 
Created attachment 2014688 [details]
File: backtrace
Comment 11 Albert Larsan 2024-02-02 20:43:54 UTC 
Created attachment 2014689 [details]
File: environ
Comment 12 Dominique Martinet 2024-02-02 21:02:43 UTC 
> 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!
Comment 13 Albert Larsan 2024-02-02 21:11:57 UTC 
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.
Comment 14 Dominique Martinet 2024-02-02 21:28:13 UTC 
> (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 :)