Bugs: Browse | Submit New | Admin

[#29222] undefined symbol: ruby_thread_data_type when starting rdebug or rdebug-ide

Date:
2011-05-23 15:38
Priority:
3
Submitted By:
Matteo Settenvini (tchernobog)
Assigned To:
Nobody (None)
Category:
None
State:
Open
Summary:
undefined symbol: ruby_thread_data_type when starting rdebug or rdebug-ide

Detailed description
Gem installed with: 

gem install ruby-debug-ide19 -- --with-ruby-include="$rvm_path/src/$(rvm tools identifier)/"

Using ruby-head at revision 31712, on a Debian amd64 box.

When launching rdebug or rdebug-ide, I get:

/home/matteo/.rvm/rubies/ruby-head/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:58:in `require':
/home/matteo/.rvm/gems/ruby-head/gems/ruby-debug-base19-0.11.25/lib/ruby_debug.so: undefined symbol: ruby_thread_data_type
- /home/matteo/.rvm/gems/ruby-head/gems/ruby-debug-base19-0.11.25/lib/ruby_debug.so (LoadError)
	from /home/matteo/.rvm/rubies/ruby-head/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:58:in `rescue in require'
	from /home/matteo/.rvm/rubies/ruby-head/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:35:in `require'
	from /home/matteo/.rvm/gems/ruby-head/gems/ruby-debug-base19-0.11.25/lib/ruby-debug-base.rb:1:in `<top
(required)>'
	from /home/matteo/.rvm/rubies/ruby-head/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
	from /home/matteo/.rvm/rubies/ruby-head/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
	from /home/matteo/.rvm/gems/ruby-head/gems/ruby-debug-ide19-0.4.12/lib/ruby-debug-ide.rb:5:in `<top (required)>'
	from /home/matteo/.rvm/gems/ruby-head/gems/ruby-debug-ide19-0.4.12/bin/rdebug-ide:9:in `require_relative'
	from /home/matteo/.rvm/gems/ruby-head/gems/ruby-debug-ide19-0.4.12/bin/rdebug-ide:9:in `<top (required)>'
	from /home/matteo/.rvm/gems/ruby-head/bin/rdebug-ide:19:in `load'
	from /home/matteo/.rvm/gems/ruby-head/bin/rdebug-ide:19:in `<main>'

"ldd ruby_debug.so":

linux-vdso.so.1 =>  (0x00007ffff8fa5000)
	libruby.so.1.9 => /home/matteo/.rvm/rubies/ruby-head/lib/libruby.so.1.9 (0x00007f88cd26f000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x00007f88cd039000)
	librt.so.1 => /lib/librt.so.1 (0x00007f88cce30000)
	libdl.so.2 => /lib/libdl.so.2 (0x00007f88ccc2c000)
	libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007f88cc9f5000)
	libm.so.6 => /lib/libm.so.6 (0x00007f88cc772000)
	libc.so.6 => /lib/libc.so.6 (0x00007f88cc3ef000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f88cd4b2000)

"nm -D libruby.so.1.9 | grep ruby_thread_data_type" returns nothing, so it appears it is not an exported symbol
from the library.

"nm libruby.so.1.9 | grep ruby_thread_data_type" in fact shows it:

000000000021c3e0 d ruby_thread_data_type

the lowercase 'd' suggests a local symbol.

Add A Comment: Notepad

Please login


Followup

Message
Date: 2011-11-30 14:01
Sender: Samuel Cochran

linecache19 0.5.13 and ruby-debug-base19 0.11.26 seem to fix
these issues. Unsure why they aren't pushed to rubygems.org.
Date: 2011-08-17 16:18
Sender: Travis Warlick

I can confirm this on OS X Lion with ruby-1.9.3-preview1 (running
under rvm). Any uodate on when this may be fixed?
Date: 2011-07-31 14:13
Sender: Guy Allard

Same here, Ruby is 1.9.3, rev 32769, on Ubuntu 11.04.

Attached Files:

Name Description Download
No Files Currently Attached

Changes:

No Changes Have Been Made to This Item