Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [dsdp-dd-dev] Failing a startup-sequence

We usually do something like:

  requestMonitor.setStatus(new Status(IStatus.ERROR, GdbPlugin.PLUGIN_ID, -1, "Cannot retrieve connection mode", e)); //$NON-NLS-1$
  requestMonitor.done();

(Taken from FinalLaunchSequence.java)

This should cause a popup window that says the launch has failed.

Marc

> -----Original Message-----
> From: dsdp-dd-dev-bounces@xxxxxxxxxxx
> [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx]On Behalf Of Jesper Eskilson
> Sent: Friday, May 30, 2008 1:11 PM
> To: Device Debugging developer discussions
> Subject: [dsdp-dd-dev] Failing a startup-sequence
> 
> 
> 
> What is the proper way to generate a failure in a 
> startup-sequence, for 
> example caused by a failure to load the debugger backend?
> 
> -- 
> /Jesper
> 
> 
> _______________________________________________
> dsdp-dd-dev mailing list
> dsdp-dd-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
> 


Back to the top