[platform-debug-dev] Question about JDIDebugTarget.initializeState()

["Raymond Qiu" <zqiu@xxxxxxx>]

Hey,

 

I have a question about the org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget#initializeState() method.

In this method, there is a piece of following code:

 

                        VirtualMachine vm = getVM();

                        if (vm != null) {

                                    try {

                                                String name = vm.name();

                                                fSupportsDisableGC = !name.equals("Classic VM"); //$NON-NLS-1$

                                    } catch (RuntimeException e) {

                                                internalError(e);

                                    }

 

I don’t understand why fSupportsDisableGC is set as true if the name of vm is not “Classic VM”? We are developing

a plug-in which have another vm which is implemented in J2ME. It does not support GC. When doing debugging, our

vm talks to eclipse vm through socket. In this code, the fSupportsDisableGC is set as true, and later on when eclipse

debugger asks our vm to disable GC, our vm returns code 99 (not supported). This caused some exception during

debugging.

 

Thanks.

 

- Raymond

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.