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
Created attachment 449851 [details] File: backtrace
(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.
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.
Hmm, strange. Did you use hibernation?
Nope, this is on a quad-core AMD desktop, freshly booted every morning. (always fully up to date)
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.
Ok. I can't reproduce it. I will close it.