Bug 561097 - [abrt] crash in ruby-1.8.6.383-6.fc12
[abrt] crash in ruby-1.8.6.383-6.fc12
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: ruby (Show other bugs)
12
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Jeroen van Meeuwen
Fedora Extras Quality Assurance
abrt_hash:44a86420cd999eae0c182784404...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-02 12:37 EST by Philip Antoniades
Modified: 2010-02-23 11:09 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-02-23 11:09:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
File: backtrace (11.24 KB, text/plain)
2010-02-02 12:37 EST, Philip Antoniades
no flags Details

  None (edit)
Description Philip Antoniades 2010-02-02 12:37:23 EST
abrt 1.0.4 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: irb '                     ' ''
comment: I was iterating through an XML doc using XML::Reader and tried to access a node I had copied earlier before closing the document. Note the steps above were the specific actions, but I will try to reproduce. 
component: ruby
executable: /usr/bin/ruby
kernel: 2.6.31.12-174.2.3.fc12.x86_64
package: ruby-1.8.6.383-6.fc12
rating: 2
reason: Process was terminated by signal 6 (Aborted)
release: Fedora release 12 (Constantine)

How to reproduce
-----
0. Create a variable n assigned to a node in an open XML document
1. Run a long while() loop in ruby assigning each node to 'n'
2. Access n after the loop has terminated
Comment 1 Philip Antoniades 2010-02-02 12:37:27 EST
Created attachment 388354 [details]
File: backtrace
Comment 2 Karel Klíč 2010-02-23 11:09:58 EST
This bug appears to have been filled using a buggy version of ABRT, because
it contains unusable backtrace. Sorry for the inconvenience.

Closing as INSUFFICIENT_DATA.

Note You need to log in before you can comment on or make changes to this bug.