[Bug 762289] New: Running YaST2/sysconfig fails with segmentation fault
https://bugzilla.novell.com/show_bug.cgi?id=762289 https://bugzilla.novell.com/show_bug.cgi?id=762289#c0 Summary: Running YaST2/sysconfig fails with segmentation fault Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: lslezak@suse.com ReportedBy: mfilka@suse.com QAContact: jsrain@suse.com Found By: --- Blocker: --- using GUI, run sysconfig module. An error dialog appeared immediately: YaST got signal 11 at YCP file /usr/share/YaST2/clients/sysconfig.ycp:24 /sbin/yast2: line 427: 20533 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS /var/log/YaST2/y2log: # sudo tail -n 0 -f /var/log/YaST2/y2log 2012-05-15 12:45:54 <1> idontknow(20161) [liby2] genericfrontend.cc(main):675 Launched YaST2 component 'y2base' 'sysconfig' 'qt' 2012-05-15 12:45:54 <1> idontknow(20161) [ui-component] YUIComponentCreator.cc(createInternal):134 Creating UI component for "" 2012-05-15 12:45:54 <1> idontknow(20161) [ui-component] YUIComponentCreator.cc(createInternal):149 Returning existing UI component for "qt" 2012-05-15 12:45:54 <1> idontknow(20161) [Y2Ruby] ruby/Y2CCRuby.cc(provideNamespace):57 Find module result: '/usr/lib64/ruby/vendor_ruby/1.8/y_lib/sysconfig.rb' 2012-05-15 12:45:54 <1> idontknow(20161) [Y2Ruby] ruby/Y2CCRuby.cc(provideNamespace):60 new ruby component 2012-05-15 12:45:54 <1> idontknow(20161) [Y2Ruby] ruby/Y2RubyComponent.cc(Y2RubyComponent):37 Creating Y2RubyComponent 2012-05-15 12:45:54 <1> idontknow(20161) [Y2Ruby] ruby/Y2CCRuby.cc(provideNamespace):63 returning existing ruby component 2012-05-15 12:45:54 <1> idontknow(20161) [Y2Ruby] ruby/Y2RubyComponent.cc(import):54 Creating namespace for import 'Sysconfig' 2012-05-15 12:45:54 <1> idontknow(20161) [Y2Ruby] ruby/Y2RubyComponent.cc(import):67 Found in '/usr/lib64/ruby/vendor_ruby/1.8/y_lib/sysconfig.rb' 2012-05-15 12:45:54 <1> idontknow(20161) [Y2Ruby] ruby/YRuby.cc(YRuby):91 Initializing ruby interpreter. 2012-05-15 12:45:54 <5> idontknow(20161) [Y2Ruby] ruby/YRuby.cc(gc_free):120 free: map size is 0 2012-05-15 12:45:54 <5> idontknow(20161) [Y2Ruby] ruby/YRuby.cc(gc_free):121 should happen quite last or we are in trouble FIXME -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=762289 https://bugzilla.novell.com/show_bug.cgi?id=762289#c1 Ladislav Slezak <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|lslezak@suse.com |jreidinger@suse.com --- Comment #1 from Ladislav Slezak <lslezak@suse.com> 2012-05-16 10:30:15 UTC --- It crashes (SIGSEGV) at import "Sysconfig"; line somewhere in ruby-bindings. Either there is a bug in yast2-ruby-bindings or your system is inconsistent (mixed RPM and SVN compiled parts). Josef, could you look at it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=762289 https://bugzilla.novell.com/show_bug.cgi?id=762289#c2 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mfilka@suse.com --- Comment #2 from Josef Reidinger <jreidinger@suse.com> 2012-05-16 10:59:29 UTC --- OK, what version of ruby bindings do you use? I know that there was bug in stack initializer that cause crash after cleaning stack which looks like is exactly what happen to you. If you use the last one, please try to run gdb with installed debug symbols and print result there ( or create scenario how to reproduce it easy way or give me ssh access so I can debug it myself ). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=762289 https://bugzilla.novell.com/show_bug.cgi?id=762289#c3 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mfilka@suse.com | --- Comment #3 from Michal Filka <mfilka@suse.com> 2012-05-17 06:33:30 UTC --- (In reply to comment #2)
OK, what version of ruby bindings do you use? # rpm -q yast2-ruby-bindings yast2-ruby-bindings-0.3.10-28.1.x86_64
scenario is described in in first post and is always reproducible. i | yast2-core-debugger | YaST2 - Core Libraries | package i | yast2-core-debuginfo | Debug information for package yast2-core | package i | yast2-core-debugsource | Debug sources for package yast2-core | package i | yast2-core-devel | YaST2 - Core Libraries | package # gdb /usr/lib/YaST2/bin/y2base (...) Reading symbols from /usr/lib/debug/usr/lib/YaST2/bin/y2base.debug...done. (gdb) run sysconfig qt (...) Program received signal SIGSEGV, Segmentation fault. 0x00007ffff4258745 in rb_require_safe () from /usr/lib64/libruby.so.1.8 (gdb) quit A debugging session is active. Inferior 1 [process 16430] will be killed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=762289 https://bugzilla.novell.com/show_bug.cgi?id=762289#c4 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #4 from Michal Filka <mfilka@suse.com> 2012-05-17 09:30:08 UTC --- Sorry, I've mixed YaST2 and Gloves during some experiments and forgot it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com