Community
Participate
Working Groups
create a 'global' status handler for no configured debugging engines. this will eventually replace the tcl specific error handler, and will be used in a forthcoming patch that will finish the implementation for bug 195206
Created attachment 73049 [details] patch implementing desired functionality
adding dependency on bug 195421
Jae, thank you for patch. I've reimplemented status handlers based on your ideas. For more information see package org.eclipse.dltk.internal.debug.ui.handlers. Now if the debugging engine is not configured (for example, path to engine not specified) you should call 'abort' method in your runner. The handler responsible for configuration errors is DebuggingEngineNotConfiguredStatusHandler. ExternalDebuggingEngineRunner is a good example of aborting debugging engine runner.
Changing OS from Mac OS to Mac OS X as per bug 185991
bulk change: fixed in 0.95