[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [dsdp-dd-dev] Basic launching question
|
Hi,
I think to remember that I've heard it already once that Eclipse plug-in
test are not working with JUnit 4. So it might not be something with you
setup ...
Regards, Uwe
Uwe Stieber, Member of Technical Staff - Sys, Wind River
direct +43 662 457915 0 fax +43 662 457915 6
> -----Original Message-----
> From: dsdp-dd-dev-bounces@xxxxxxxxxxx
> [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc
> Khouzam (QA/EMC)
> Sent: Wednesday, July 04, 2007 4:30 PM
> To: Device Debugging developer discussions
> Subject: RE: [dsdp-dd-dev] Basic launching question
>
> Hi again,
>
> Just for fun, I tried the same thing with JUnit 3 and I got further.
> I guess my Junit 4 setup has a problem.
>
> I'll stick to JUnit 3 for now.
>
> Thanks
>
> -----Original Message-----
> From: dsdp-dd-dev-bounces@xxxxxxxxxxx
> [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx]On Behalf Of Stieber, Uwe
> Sent: Wednesday, July 04, 2007 9:54 AM
> To: Device Debugging developer discussions
> Subject: RE: [dsdp-dd-dev] Basic launching question
>
>
> Hi,
> you need to use "JUnit Plug-in Test".
>
> Best regards,
>
> Uwe Stieber, Member of Technical Staff - Sys, Wind River
> direct +43 662 457915 0 fax +43 662 457915 6
>
>
>
>
> > -----Original Message-----
> > From: dsdp-dd-dev-bounces@xxxxxxxxxxx
> > [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc
> > Khouzam (QA/EMC)
> > Sent: Wednesday, July 04, 2007 3:51 PM
> > To: dsdp-dd-dev@xxxxxxxxxxx
> > Subject: [dsdp-dd-dev] Basic launching question
> >
> > Hi,
> >
> > I am trying to trigger the GDB/MI launch programmatically
> > from a JUnit plugin. I have looked at some articles and
> > the example code of JUnit tests and I'm trying to do the same
> > basic call, but I'm getting a null pointer exception.
> > Basically, I try to get the LaunchManager by calling:
> >
> > ILaunchManager launchMgr =
> > DebugPlugin.getDefault().getLaunchManager();
> >
> > But the DebugPlugin.getDefault() is null.
> > I'm guessing I have to launch my own JUnit tests in a certain
> > way to trigger the DebugPlugin to be instantiated?
> > I'm launching my tests by doing DebugAs->JUnit Test
> >
> > Any ideas?
> >
> > Thanks
> >
> _______________________________________________
> dsdp-dd-dev mailing list
> dsdp-dd-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
> _______________________________________________
> dsdp-dd-dev mailing list
> dsdp-dd-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
>
