Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tcf-dev] Extended breakpoint stop reasons proposal 
Hi Renan,

There is an easier way to change what we show to a user: the context state contains triggered breakpoint ID, so client side knows what kind of breakpoint was triggered, it can easily show this information to the user. I do feel that showing just "Breakpoint" in the debug view is not sufficient, but I'm not sure what is the best format to present more useful information. Note, that multiple breakpoints of different types can be triggered at same time, so presenting info about all of them might not be trivial.

Regards,
Eugene

-----Original Message-----
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Renan Le Padellec
Sent: Tuesday, October 16, 2012 2:51 AM
To: TCF Development (tcf-dev@xxxxxxxxxxx)
Subject: [tcf-dev] Extended breakpoint stop reasons proposal

Hello,

In February, the Breakpoints service has been modified to support the
"EventType" and "EventArgs" attributes for event breakpoints. When such
breakpoints are triggered, the stop reason of the context suspend event
sent by the agent is the same than a classic breakpoint (i.e
Breakpoint). From an user point of view, it might be useful to see a
stop reason that describes the specific event breakpoint. What do you think?

My proposal is to add an API at the context level (i.e
context_get_extended_breakpoint_stop_reasons()) to return the stop
reason(s) of the event breakpoint.

/*
  * Get extended breakpoint stop reasons
  * Return one or more breakpoint stop reasons.
  * If no context specific reason is found, return NULL as default.
  */

#if ENABLE_ExtendedBreakpointStopReasons
extern const char * context_get_extended_breakpoint_stop_reasons(Context
* ctx);
#endif


Regards,
Renan
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/tcf-dev



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

Back to the top