unresolved external symbol _ruby_current_thread (why I can't build linecache on Windows)

20 views
Skip to first unread message

Eric Promislow

unread,
Apr 11, 2013, 12:20:00 PM4/11/13
to rubyin...@googlegroups.com
I should have used a more expressive subject.  Please see the "can't build linecache" post for the details

Luis Lavena

unread,
Apr 11, 2013, 12:21:57 PM4/11/13
to rubyin...@googlegroups.com
Hello Eric,

On Thu, Apr 11, 2013 at 12:20 PM, Eric Promislow <eric.pr...@gmail.com> wrote:
I should have used a more expressive subject.  Please see the "can't build linecache" post for the details

I'm not sure about linecache, but I think is no longer necessary, considering the changes done to Trace API in Ruby 2.0

There are several threads at ruby-core and issues at Redmine discussing those changes.

There is also a debugger gem that works with Ruby 2.0 without the need of monkey-patching it.

Have you took a look to that?
 
--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyinstalle...@googlegroups.com.
To post to this group, send email to rubyin...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry

Eric Promislow

unread,
Apr 11, 2013, 12:40:39 PM4/11/13
to rubyin...@googlegroups.com
I'm trying to get Komodo's debugger client working with Ruby 2.0 and the ruby-debug-base wrapper around ruby_debug.so, and it still uses linecache. I looked at debugger, koichi's fork of ruby-debug-base,  and also denofevil's debase, and got my original code working on Linux with cldwalker's slightly updated fork of the classic ruby-debug-base.

Any idea why the Linux build doesn't complain about rb_current_thread and Windows does?


--
You received this message because you are subscribed to a topic in the Google Groups "RubyInstaller" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rubyinstaller/pA2Azfxq8aA/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to rubyinstalle...@googlegroups.com.

Eric Promislow

unread,
Apr 11, 2013, 5:44:40 PM4/11/13
to rubyin...@googlegroups.com
Fixed by installing the rubyinstaller bits, and using them to build the library.
Makes sense, as our Windows bits have always required the ruby-installer
version of Ruby.

- Eric
Reply all
Reply to author
Forward
0 new messages