Bug 1591581

Summary: [abrt] ruby: die(): ruby-mri killed by SIGABRT
Product: [Fedora] Fedora Reporter: Paulo Fidalgo <paulo.fidalgo.pt>
Component: rubyAssignee: Vít Ondruch <vondruch>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: jaruga, mo, mtasaka, paulo.fidalgo.pt, pvalena, s, strzibny, vanmeeuwen+fedora, vondruch
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/202a255d689716eafafc4dbe6a4ec8dfddc034d9
Whiteboard: abrt_hash:e78ba53b5d60bcb185d1837a640314855bee5639;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-15 13:11:52 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: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Paulo Fidalgo 2018-06-15 04:27:43 UTC 
Version-Release number of selected component:
ruby-2.5.1-93.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 3
cmdline:        spring app    | registadora | started 3 secs ago | development mode
crash_function: die
executable:     /usr/bin/ruby-mri
journald_cursor: s=82782adf68df4c0aaa10595ce943de29;i=273a26;b=5d25b8c1d1bd4036a8c7fad059276e24;m=1022ab6834;t=56ea6906b75f4;x=be6bd1d35a4a2f42
kernel:         4.16.14-300.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 Paulo Fidalgo 2018-06-15 04:27:47 UTC 
Created attachment 1451719 [details]
File: backtrace
Comment 2 Paulo Fidalgo 2018-06-15 04:27:49 UTC 
Created attachment 1451720 [details]
File: cgroup
Comment 3 Paulo Fidalgo 2018-06-15 04:27:51 UTC 
Created attachment 1451721 [details]
File: core_backtrace
Comment 4 Paulo Fidalgo 2018-06-15 04:27:53 UTC 
Created attachment 1451722 [details]
File: cpuinfo
Comment 5 Paulo Fidalgo 2018-06-15 04:27:54 UTC 
Created attachment 1451723 [details]
File: dso_list
Comment 6 Paulo Fidalgo 2018-06-15 04:27:56 UTC 
Created attachment 1451724 [details]
File: environ
Comment 7 Paulo Fidalgo 2018-06-15 04:27:58 UTC 
Created attachment 1451725 [details]
File: limits
Comment 8 Paulo Fidalgo 2018-06-15 04:28:00 UTC 
Created attachment 1451726 [details]
File: maps
Comment 9 Paulo Fidalgo 2018-06-15 04:28:01 UTC 
Created attachment 1451727 [details]
File: mountinfo
Comment 10 Paulo Fidalgo 2018-06-15 04:28:04 UTC 
Created attachment 1451728 [details]
File: open_fds
Comment 11 Paulo Fidalgo 2018-06-15 04:28:05 UTC 
Created attachment 1451729 [details]
File: proc_pid_status
Comment 12 Jun Aruga 2018-06-15 12:37:09 UTC 
Do you know how we can reproduce it?
Comment 13 Vít Ondruch 2018-06-15 13:11:52 UTC 
It seems there is FFI involved in your crash, so something which is using FFI for some library binding is probably not working properly. I don't think there is anything we can do about it.