[katello-devel] ruby segmentation fault during Add Permission from UI

Brad Buckingham bbuckingham at redhat.com
Mon Jul 11 20:44:25 UTC 2011


Team,

We are encountering a segmentation fault from ruby when attempting to 
'Add Permission' to a Role from the UI.  This does not occur 100% of the 
time; however, it seems to be fairly easy to recreate.

The config is:
- F14 development configuration (Note: we have not encountered this 
issue with an F15 configuration)

The scenario is:
- create a new role (Administration -> Roles -> New Role)
- attempt to add a permission to the role (select role just created, 
click 'Add Permission')

It is clicking the 'Add Permission' that triggers the fault.  The 
request initiated is:
- https://<server>/roles/show_permission?role_id=7

The segmentation fault appears to occur almost immediately (e.g. before 
entering the controller action) and is not always in the same place.  
The following are a few examples:

example 1: (this is the most frequent...)

/usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/core_ext/module/remove_method.rb:3: 
[BUG] Segmentation fault
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux]

example 2:

/usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/inflector/inflections.rb:151: 
[BUG] Segmentation fault
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux]

example 3:

/usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/core_ext/module/remove_method.rb:9: 
[BUG] Segmentation fault
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux]

example 4:

/usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/core_ext/class/attribute.rb:73: 
[BUG] rb_gc_mark(): unknown data type 0x37(0x493e8e0) non object
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux]


Any thoughts as to what may be causing this behavior?  I suspect it 
could be an issue with the gems being used; however, it seems odd that 
it has only been observed in this single scenario (so far).

Soliciting your ideas/input in to the potential cause of this mysterious 
fault.... :)

thanks,
Brad




More information about the katello-devel mailing list