Hi Joe, I'm relieved (maybe relieved is the wrong word), to hear, that I'm not the only one who is suffering from the slow debugger. I had a quick look into eclipseDebug.rb some time ago and asked, if porting eclipseDebug to C could be a solution. As noone has answered :-(, I ceased examining the debugger.
What I've found up to now: - eclipseDebug.rb installs a traceProc (set_trace_func at the end of the file) - the traceProc is called for every event that occurs in the interpreter (e.g. every line, c-call, c-return, ...). So this probably is the place that eats up all the time. I guess the trace_func is evaluated in toplevel - context, so the profiler shows it as #toplevel - you can check, that the trace_proc causes the delay, if you comment out the set_trace_func command at the end of eclipseDebug (but the debugger is rather useless after this). Maybe the original author of eclipseDebug.rb could give us a hint where to start improving the debugger? Implementing the whole debugger as C-Code? Implementing only the trace_proc in C? Or removing the trace_proc at all (ruby seems to have build in debugging facilities) Best regards Dirk -- 10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail +++ GMX - die erste Adresse für Mail, Message, More +++ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
