Bug 1089693

Summary: [abrt] grsync: g_malloc0(): grsync killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Ernie D <wagnered>
Component: grsyncAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/dd1dd7cff0fe99a2a07c106ab91414c35ed8e7a2
Whiteboard: abrt_hash:51ff1f772b5444f896273215b0529ec6f383b03d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:13:12 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Ernie D 2014-04-21 16:44:15 UTC 
Description of problem:
What I do know is that there is a lot of data to back up so I left it running overnight.  When I checked in the morning, it wasn't running.

Also, I was backing up to an NFS share.

Version-Release number of selected component:
grsync-1.2.4-2.fc20

Additional info:
reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        grsync -i
crash_function: g_malloc0
executable:     /usr/bin/grsync
kernel:         3.13.9-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_malloc0 at gmem.c:134
 #3 gtk_mark_segment_new at gtktextmark.c:337
 #4 gtk_text_mark_init at gtktextmark.c:106
 #5 g_type_create_instance at gtype.c:1868
 #6 g_object_new_internal at gobject.c:1746
 #7 g_object_new_valist at gobject.c:2002
 #9 gtk_text_mark_new at gtktextmark.c:212
 #10 real_set_mark at gtktextbtree.c:2782
 #11 _gtk_text_btree_set_mark at gtktextbtree.c:2830
 #12 gtk_text_buffer_set_mark at gtktextbuffer.c:2045
Comment 1 Ernie D 2014-04-21 16:44:18 UTC 
Created attachment 888136 [details]
File: backtrace
Comment 2 Ernie D 2014-04-21 16:44:20 UTC 
Created attachment 888137 [details]
File: cgroup
Comment 3 Ernie D 2014-04-21 16:44:21 UTC 
Created attachment 888138 [details]
File: core_backtrace
Comment 4 Ernie D 2014-04-21 16:44:23 UTC 
Created attachment 888139 [details]
File: dso_list
Comment 5 Ernie D 2014-04-21 16:44:24 UTC 
Created attachment 888140 [details]
File: environ
Comment 6 Ernie D 2014-04-21 16:44:26 UTC 
Created attachment 888141 [details]
File: exploitable
Comment 7 Ernie D 2014-04-21 16:44:27 UTC 
Created attachment 888142 [details]
File: limits
Comment 8 Ernie D 2014-04-21 16:44:29 UTC 
Created attachment 888143 [details]
File: maps
Comment 9 Ernie D 2014-04-21 16:44:30 UTC 
Created attachment 888144 [details]
File: open_fds
Comment 10 Ernie D 2014-04-21 16:44:31 UTC 
Created attachment 888145 [details]
File: proc_pid_status
Comment 11 Ernie D 2014-04-21 16:44:35 UTC 
Created attachment 888146 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-05-29 11:38:09 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 13 Fedora End Of Life 2015-06-29 20:13:12 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.