Re: [jdt-debug-dev] Pluggable JDI implementations

["Darin Wright" <Darin_Wright@xxxxxxx>]

Ideally, our debugger would work with any JDI v1.4 compatible implementation (perhaps even v1.3, if we decide to use reflection to see if HCR is present). 

Currently, we have some reliance on our JDI implementation - when I try to use the Sun implementation I get some exceptions. When I examined the code a little, I found we are making some "illegal" calls to StackFrame.location(). We make this call after a stack frame has become invalid (thread has resumed), in StackFrame.equalFrame(...). Our JDI implementation caches the location for stack frames, and does not adhere to the JDI spec (i.e. throw an InvalidStackFrameException, once its thread had resumed).

Realistically, we can only test on a few JDI implementations that are publically available.

Darin

Jared Burns <jared-eclipse@xxxxxxxxx> Sent by: jdt-debug-dev-admin@xxxxxxxxxxx 08/21/2002 09:12 AM Please respond to jdt-debug-dev

To:        jdt-debug-dev@xxxxxxxxxxx         cc:                 Subject:        [jdt-debug-dev] Pluggable JDI implementations

In bug 22611 (<http://bugs.eclipse.org/bugs/show_bug.cgi?id=22611>), Darin W 
mentions that one of our goals is to support other JDI implementations. 
Darin, I'm curious to know exactly how far you'd like to take this. Are you 
thinking you'd like to make the JDI client pluggable by end users?

Everyone else, I'm curious to know if anyone has a use for this feature. 
Would a (supported) pluggable JDI client story be of interest?

Thanks,
- Jared
_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-debug-dev