Re: [jdt-debug-dev] Question regarding JDIDebugTarget constructor.

[Darin Wright <Darin_Wright@xxxxxxxxxx>]

Also note, you should be using the API
method on JDIDebugModel to create a debug target, rather than the internal
(non-API) constructor:

JDIDebugModel {
...
        public
static IDebugTarget newDebugTarget(final ILaunch launch, final VirtualMachine
vm, final String name, final IProcess process, final boolean allowTerminate,
final boolean allowDisconnect, final boolean resume)
...
}

Darin Wright
Eclipse Debug Lead,
Rational Team,
IBM Canada
(204)938-8051

"Giuliano Mega" <giuliano.mega@xxxxxxxxx>
Sent by: jdt-debug-dev-bounces@xxxxxxxxxxx

06/08/2006 09:36 AM

Please respond to
"Eclipse JDT Debug developers list."

To	"Eclipse JDT Debug developers list." <jdt-debug-dev@xxxxxxxxxxx>
cc
Subject	[jdt-debug-dev] Question regarding JDIDebugTarget constructor.

Hi!

While going through
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget code, I
realized that its constructor requires you to pass both the launch and
the process as parameters:

public JDIDebugTarget(ILaunch launch, VirtualMachine jvm, String name,
boolean supportTerminate, boolean supportDisconnect, IProcess process,
boolean resume)

Why do I have to pass both? Would there be any issues if I used
process.getLaunch() instead?

Thanks in advance,

-- 
Giuliano Mega <giuliano@xxxxxxxxxx>
_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-debug-dev