Re: [RDT-Dev] Ruby-debug integration
Markus, That's great to hear - good job on cranking out all those fixes and updates to the debugger! Outside of this work do we have any other outstanding stuff to be looked at for the 0.9.0? I took a stab at the unit tests and they look mostly right. The two tests for regular expression syntax coloring both fail, but they have always and I'm not sure we're going to get them to work by 0.9.0 (or until we hve a much smarter way to write up rules for Eclipse syntax coloring). The other failing test is for the interpreter stuff, and until I have a linux machine that can reproduce the error I'm not sure if I can nail what's going on. Essentially the libraries it's detecting are missing the set of core stubs that get generated when you first add an interpreter. I don't know if there's just some oddity going on with the test on the build machine - or if those stubs aren't getting generated and added to the library list on Linux (I'm guessing the former, since this works on Mac OSX). Thanks, Chris On 2/26/07, Markus Barchfeld [EMAIL PROTECTED] wrote: Hi! Below you find the status of ruby-debug functionality in the current nightly builds. I have developed and tested on Linux (ubuntu) only, and would be interested to hear how it works on OS X and Windows (C compiler needed, please have a look at the forum, too). Currently there is still a patched version of ruby-debug necessary. I am trying to synchronize our release with Kent, so that there will be a compatible ruby-debug release for the RDT 0.9.0 release or release candidate. My next topic will be to update the threads in the Launch view regularly. I think the remaining TODO's can be fixed within 2 days except for the last one which we probably have to postpone after 0.9.0. Thanks Markus OK: * adding/removing breakpoints (including first line) before and during debug session * Setting/clearing a catchpoint * stepping (step into/over/return, resume) * Variables view * Inspect/inspect... from editor; errors are displayed via job return status * Ruby inspect from Display view * code reloading on editor save TODO: * perspective switch after suspension is unreliable * the Variables View does not show class variables and constants * Threads are not updated in between suspensions and particularly after the session has started. So there are no threads shown until the first suspension and after resuming the thread list will keep its state until the next suspension. * code reloading job can not be canceled * Threads can not be suspended manually (the suspend button in the Launch view is always disabled) - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development -- http://cwilliams.textdriven.com - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Ruby-debug integration
Outside of this work do we have any other outstanding stuff to be looked at for the 0.9.0? [] Only some cleanup: It still seems as if there are two sets of constants which are used as keys in the launch configuration. Could we merge them? The other failing test is for the interpreter stuff, and until I have a linux machine that can reproduce the error I'm not sure if I can nail what's going on. Essentially the libraries it's detecting are missing the set of core stubs that get generated when you first add an interpreter. I don't know if there's just some oddity going on with the test on the build machine - or if those stubs aren't getting generated and added to the library list on Linux (I'm guessing the former, since this works on Mac OSX). OK, I can check this error. Thanks Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Ruby-debug integration
Christopher Williams wrote: Outside of this work do we have any other outstanding stuff to be looked at for the 0.9.0? I'm not perfectly up to date with the SVN (from a few days) but I remember that the HyperlinkDetector code wasn't activated in the plugin.xml. Also, in my local copy, the Open Definition (F3 on selection) doesn't seem to do anything... is still deactivated for 0.9? murphee - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Ruby-debug integration
murphee, On 2/26/07, Werner Schuster (murphee) [EMAIL PROTECTED] wrote: Christopher Williams wrote: Outside of this work do we have any other outstanding stuff to be looked at for the 0.9.0? I'm not perfectly up to date with the SVN (from a few days) but I remember that the HyperlinkDetector code wasn't activated in the plugin.xml. Also, in my local copy, the Open Definition (F3 on selection) doesn't seem to do anything... is still deactivated for 0.9? Good catch. I've enabled it in plugin.xml and I've also modified the code to behave like the Go to Declaration stuff. That stuff shopul dbe working fine. It won't typically find anything until after the Search Index Job finishes. I run a job when the project is opened which indexes all the globals and types. Until that list is built, most code resolution won't work (because we usually infer a type and then look it up in the index). Thanks, Chris -- http://cwilliams.textdriven.com - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Ruby-debug integration
Markus, all, On 2/26/07, Markus Barchfeld [EMAIL PROTECTED] wrote: Outside of this work do we have any other outstanding stuff to be looked at for the 0.9.0? [] Only some cleanup: It still seems as if there are two sets of constants which are used as keys in the launch configuration. Could we merge them? Yes, we should be able to. I took a firsts tab at it and deprecated the old constants, pointed them at their new replacement constants and retained the same underlying string when possible to aim for backwards compatibility some. The next step is to clean up the code that refers to the old constants, remove it and then remove the old interface. Thanks, Chris -- http://cwilliams.textdriven.com - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
