[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] catchpoints
|
All action should use "visibleWhen" to check if catchpoints are
supported in general by the underlying context.
I also think event types can be contributed via an extension point, but
this is open for discussion, of course.
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Elena Laskavaia
Sent: Tuesday, April 08, 2008 3:21 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] catchpoints
This is the most tricky part. Short answer is for gdb is close to
impossible to do.
For example to know if gdb support catchpoints you not only need to
start gdb but you also have to start program. I was thinking making ui
(i.e. Add catchpoint... dialog) always show up and let backed return not
supported operation in attempt to use particular unsupported event
catchpoint.
As what is showing up in the dialog as events: I think we let debugger
plugin to contribute events, so technically if debugger does not
contribute anything it won't show up.
Mikhail Khodjaiants wrote:
>
> Speaking seriously, please make sure the UI for this functionality
> doesn't appear if a backend doesn't support it.
>
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
