Red Hat Bugzilla – Bug 577955
[abrt] crash in ruby-188.8.131.523-6.fc12: Process /usr/bin/ruby was killed by signal 6 (SIGABRT)
Last modified: 2010-11-08 12:54:19 EST
abrt 1.0.8 detected a crash.
Attached file: backtrace
cmdline: /usr/bin/ruby '-e p(Process.pid.to_s)' '-e load(ARGV.shift)' -I /home/tata/workspace/.metadata/.plugins/org.rubypeople.rdt.launching/ruby/flush -rrdt_stream_sync.rb -- /usr/bin/rdebug-ide --port 49371 script/server -- mongrel --port=3000 --environment=development
comment: Was debugging very simple RUBY application, going through core libriaries
reason: Process /usr/bin/ruby was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Created attachment 403358 [details]
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 WONTFIX if it remains open with a Fedora
'version' of '12'.
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 prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
*** This bug has been marked as a duplicate of bug 633830 ***
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #633830.
Sorry for the inconvenience.