Bug 1145757

Summary: [abrt] weechat: __pthread_mutex_cond_lock(): weechat killed by SIGABRT
Product: [Fedora] Fedora Reporter: Robbie Harwood <rharwood>
Component: weechatAssignee: Paul P Komkoff Jr <i>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: chandanrmail, hello, i, jamielinux, karlthered, niveusluna, rharwood
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3b249b40f3086638cf193461d88c0256d136ece8
Whiteboard: abrt_hash:55983e11b55a4b047e2be3c29c34c024ad021f1e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-26 14:43:57 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: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Robbie Harwood 2014-09-23 16:22:11 UTC 
Description of problem:
I ran weechat as normal and it tripped an assert about being the owner of a pthread mutex.  I cannot reproduce this easily.

Version-Release number of selected component:
weechat-1.0-3.fc22

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        weechat
crash_function: __pthread_mutex_cond_lock
executable:     /usr/bin/weechat
kernel:         3.17.0-0.rc6.git0.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            21259

Truncated backtrace:
Thread no. 1 (5 frames)
 #4 __pthread_mutex_cond_lock at ../nptl/pthread_mutex_lock.c:81
 #5 pthread_cond_wait@@GLIBC_2.3.2 at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:259
 #6 GC_wait_marker at pthread_support.c:2036
 #7 GC_help_marker at mark.c:1168
 #8 GC_mark_thread at pthread_support.c:389
Comment 1 Robbie Harwood 2014-09-23 16:22:14 UTC 
Created attachment 940495 [details]
File: backtrace
Comment 2 Robbie Harwood 2014-09-23 16:22:15 UTC 
Created attachment 940496 [details]
File: cgroup
Comment 3 Robbie Harwood 2014-09-23 16:22:17 UTC 
Created attachment 940497 [details]
File: core_backtrace
Comment 4 Robbie Harwood 2014-09-23 16:22:18 UTC 
Created attachment 940498 [details]
File: dso_list
Comment 5 Robbie Harwood 2014-09-23 16:22:20 UTC 
Created attachment 940499 [details]
File: environ
Comment 6 Robbie Harwood 2014-09-23 16:22:21 UTC 
Created attachment 940500 [details]
File: limits
Comment 7 Robbie Harwood 2014-09-23 16:22:22 UTC 
Created attachment 940501 [details]
File: maps
Comment 8 Robbie Harwood 2014-09-23 16:22:23 UTC 
Created attachment 940502 [details]
File: open_fds
Comment 9 Robbie Harwood 2014-09-23 16:22:25 UTC 
Created attachment 940503 [details]
File: proc_pid_status
Comment 10 Robbie Harwood 2014-09-23 16:22:26 UTC 
Created attachment 940504 [details]
File: var_log_messages
Comment 11 Jaroslav Reznik 2015-03-03 16:19:19 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 12 Peter Borsa 2015-03-24 13:11:16 UTC 
Hi!

What about this issue? Could you reproduce it again?
Comment 13 Robbie Harwood 2015-05-26 14:43:57 UTC 
Apologies, I no longer have access to this machine.