Bug 637725

Summary: [abrt] bash-4.1.7-1.fc13: raise: Process /bin/bash was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Antoine Martin <antoine>
Component: bashAssignee: Roman Rakus <rrakus>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: rrakus, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:93e742ea40a4b18b093a8decb6f7686612f48e76
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-27 11:28:13 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

Description Antoine Martin 2010-09-27 08:58:28 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: bash
comment: Not sure if this is at all relevant, but the line's quotes were imbalanced.
component: bash
crash_function: raise
executable: /bin/bash
kernel: 2.6.34.7-56.fc13.x86_64
package: bash-4.1.7-1.fc13
rating: 4
reason: Process /bin/bash was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1285577765
uid: 500

How to reproduce
-----
1. Cut & paste a long line
Comment 1 Antoine Martin 2010-09-27 08:58:34 UTC 
Created attachment 449851 [details]
File: backtrace
Comment 2 Roman Rakus 2010-09-27 09:40:35 UTC 
(In reply to comment #0)
> abrt version: 1.1.13
> architecture: x86_64
> Attached file: backtrace
> cmdline: bash
> comment: Not sure if this is at all relevant, but the line's quotes were
> imbalanced.
> component: bash
> crash_function: raise
> executable: /bin/bash
> kernel: 2.6.34.7-56.fc13.x86_64
> package: bash-4.1.7-1.fc13
> rating: 4
> reason: Process /bin/bash was killed by signal 6 (SIGABRT)
> release: Fedora release 13 (Goddard)
> time: 1285577765
> uid: 500
> 
> How to reproduce
> -----
> 1. Cut & paste a long line

Can you please say what is on that line? Also, the history could help here.
Comment 3 Antoine Martin 2010-09-27 09:52:14 UTC 
bash history doesn't have anything unusual:

cd projects/shifter/trunk/
./release/local-install.sh; ./tests/conch_util_test.py 
./bin/viper.sh 
./bin/virtual.sh 
cd
cat Documents/Galaxy-Codes.txt 
./bin/pts.sh 
cd
./bin/virtual.sh 
rsync --append-verify --bwlimit=20000 -rplogtv --progress somehost:~/somefile ./Vi
rsync --append-verify --bwlimit=20000 -rplogtv --progress somehost:~/somefile ./Vi; rsync --append-verify --bwlimit=20000 -rplogtv --progress somehost:~/somefile ./Videos/

The rsync line is the offending one, was trying to run the last one (the one going to Videos/) but bash was behaving really slowly expanding "./Vi" with tab, so somehow I ended up pasting the rsync again at the end of the same line (no idea how).
When I saw that, I simply tried to copy the correct rsync incantation (the last one) - and that's when bash segfaulted.
Comment 4 Roman Rakus 2010-09-27 10:20:46 UTC 
Hmm, strange. Did you use hibernation?
Comment 5 Antoine Martin 2010-09-27 10:23:28 UTC 
Nope, this is on a quad-core AMD desktop, freshly booted every morning. (always fully up to date)
Comment 6 Antoine Martin 2010-09-27 10:39:39 UTC 
This is probably the first time I have ever seen bash crash on me like this, so unless the backtrace gives you anything meaningful I would be tempted to blame this one on cosmic rays until someone else can come up with anything better.
Comment 7 Roman Rakus 2010-09-27 11:28:13 UTC 
Ok. I can't reproduce it. I will close it.