Bug 1166666

Summary: [abrt] nano: delete_node(): nano killed by SIGABRT
Product: [Fedora] Fedora Reporter: tiantangzhifeng
Component: nanoAssignee: David Woodhouse <dwmw2>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dwmw2, jaswinder, kdudka
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/95eccd2309c44ed2a07fd445353c14d93b0bc219
Whiteboard: abrt_hash:772f3c07e69104f2da24b2f8367f884684a13b7e
Fixed In Version: nano-2.3.2-5.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-03 01:05:02 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 tiantangzhifeng 2014-11-21 12:52:26 UTC 
Description of problem:
When using the experimental undo feature in nano, it will occur occasionally.

Version-Release number of selected component:
nano-2.3.2-4.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        nano test.c
crash_function: delete_node
executable:     /usr/bin/nano
kernel:         3.17.2-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #5 delete_node at nano.c:128
 #6 free_filestruct at nano.c:170
 #7 add_undo at text.c:869
 #8 update_undo at text.c:1051
 #9 do_output at nano.c:1996
 #10 do_input at nano.c:1625
Comment 1 tiantangzhifeng 2014-11-21 12:52:31 UTC 
Created attachment 959693 [details]
File: backtrace
Comment 2 tiantangzhifeng 2014-11-21 12:52:32 UTC 
Created attachment 959694 [details]
File: cgroup
Comment 3 tiantangzhifeng 2014-11-21 12:52:34 UTC 
Created attachment 959695 [details]
File: core_backtrace
Comment 4 tiantangzhifeng 2014-11-21 12:52:35 UTC 
Created attachment 959696 [details]
File: dso_list
Comment 5 tiantangzhifeng 2014-11-21 12:52:36 UTC 
Created attachment 959697 [details]
File: environ
Comment 6 tiantangzhifeng 2014-11-21 12:52:37 UTC 
Created attachment 959698 [details]
File: limits
Comment 7 tiantangzhifeng 2014-11-21 12:52:39 UTC 
Created attachment 959699 [details]
File: maps
Comment 8 tiantangzhifeng 2014-11-21 12:52:40 UTC 
Created attachment 959700 [details]
File: open_fds
Comment 9 tiantangzhifeng 2014-11-21 12:52:41 UTC 
Created attachment 959701 [details]
File: proc_pid_status
Comment 10 tiantangzhifeng 2014-11-21 12:52:43 UTC 
Created attachment 959702 [details]
File: var_log_messages
Comment 11 Kamil Dudka 2014-11-21 15:50:22 UTC 
Thanks for the bug report!  I will try to apply the upstream patch to fix it:

http://savannah.gnu.org/bugs/?25585
Comment 12 Fedora Update System 2014-11-21 16:44:11 UTC 
nano-2.3.2-5.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/nano-2.3.2-5.fc20
Comment 13 Fedora Update System 2014-11-22 12:37:26 UTC 
Package nano-2.3.2-5.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing nano-2.3.2-5.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-15520/nano-2.3.2-5.fc20
then log in and leave karma (feedback).
Comment 14 Fedora Update System 2014-12-03 01:05:02 UTC 
nano-2.3.2-5.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.