Bug 1145757 - [abrt] weechat: __pthread_mutex_cond_lock(): weechat killed by SIGABRT
Summary: [abrt] weechat: __pthread_mutex_cond_lock(): weechat killed by SIGABRT
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: weechat
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul P Komkoff Jr
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:55983e11b55a4b047e2be3c29c3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-23 16:22 UTC by Robbie Harwood
Modified: 2015-05-26 14:43 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-26 14:43:57 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (68.54 KB, text/plain)
2014-09-23 16:22 UTC, Robbie Harwood 		no flags Details
File: cgroup (191 bytes, text/plain)
2014-09-23 16:22 UTC, Robbie Harwood 		no flags Details
File: core_backtrace (21.09 KB, text/plain)
2014-09-23 16:22 UTC, Robbie Harwood 		no flags Details
File: dso_list (5.91 KB, text/plain)
2014-09-23 16:22 UTC, Robbie Harwood 		no flags Details
File: environ (1.56 KB, text/plain)
2014-09-23 16:22 UTC, Robbie Harwood 		no flags Details
File: limits (1.29 KB, text/plain)
2014-09-23 16:22 UTC, Robbie Harwood 		no flags Details
File: maps (29.61 KB, text/plain)
2014-09-23 16:22 UTC, Robbie Harwood 		no flags Details
File: open_fds (390 bytes, text/plain)
2014-09-23 16:22 UTC, Robbie Harwood 		no flags Details
File: proc_pid_status (987 bytes, text/plain)
2014-09-23 16:22 UTC, Robbie Harwood 		no flags Details
File: var_log_messages (184 bytes, text/plain)
2014-09-23 16:22 UTC, Robbie Harwood 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.