rubinius

Comments and changes to this ticket

• 

  Eero Saynatkari December 17th, 2007 @ 02:08 PM

  • → State changed from “new” to “open”

  Actually, we can probably already do this. Basically we are just dealing with backtraces.

  Look at CompiledMethod in kernel/core/compiled_method.rb. We already have the #file and #line_from_ip methods that pretty much give us the info we need. #file is self-explanatory and then:

    some_method.line_from_ip 0 
  

  Can be used to find the first line of the method and I cannot test until I get home (I think, you may need to use 1 instead.)

  Also, MethodContext from kernel/core/context.rb defines MethodContext#file and MethodContext#line are both proxy methods that use the currently executing @CompiledMethod@'s interface (convenience method #location also exists.)

  So that already tells us where the method is defined. Secondly, we wanted to know where it is being called? For that, of course, there already is Kernel.caller (standard MRI too), but you can access it slightly more programmatically:

    sender = MethodContext.current.sender
    p sender.file, sender.line
    cm = sender.method
    p cm.file, cm.line_from_ip(0)
  

  Tadaa!

  Is this the part where you tell me I completely misunderstood what you are talking about?

• 

  Kevin Clark December 17th, 2007 @ 02:11 PM

  Oh rue, you make me so happy. That's basically what I was looking for. I'm going to do some hacking and see if I can't come up with some nice helpers to handle that. Maybe a command line interface to load up libs, and then tell where a block of code's methods come from.

• 

  Eero Saynatkari January 8th, 2008 @ 11:34 AM

  • → State changed from “open” to “resolved”

  Closing since my awesomeness saved the day here. CM and MC are working nicely in HEAD.