|
| Re: Runtime diagnostic/debugging strategies. [message #157139 is a reply to message #155923] |
Fri, 14 November 2003 21:16  |
Eclipse User |
|
|
|
Originally posted by: John_Arthorne.oti.com_
The Eclipse tracing support is enabled by:
- Putting a file called ".options" in the Eclipse install directory
- Running eclipse with "-debug" command line argument.
The flags that go into the .options file are specified by various
plugins. Each plugin that uses tracing publishes a template ".options"
file in their plugin install directory that lists and describes all the
flags. Search the plugins directory for files called ".options" to see
what's there. If you want to add your own trace options, the API to use
is Plugin.isDebugging and Platform.getDebugOption. Look through Eclipse
source for examples on how they are used (for example
org.eclipse.core.runtime plugin).
--
Mike McGowan wrote:
> I have developed several Eclipse plugins and delivered them as a packaged
> application. On some machines the application hangs. My basic question is
> what can be done to diagnosis a delivered application. e.g. commanline
> startup options, etc.
>
> I'm familiar and have used the tracing support within the PDE, can this
> facility be used in a delivered application? I've also read the javadoc on
> ILog & ILogListener and wonder if those provide some support? Perhaps
> better than seeking specific answers here would be references to Eclipse
> articles, books, Javadoc that I need to read before implementing a generic
> strategy.
>
> TIA,
> Mike
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03313 seconds
] 
Search
Help
Register
Login
Home
