Re: [tcf-dev] breakpoints / access types

[Eugene Tarassov <eugene.tarassov@xxxxxxxxxx>]

Hi Samuel,

When breakpoint type is "Auto", the breakpoints service asks debugger backend to plant it as hardware bp. If backend rejects the request and returns ERR_UNSUPPORTED, it is planted as software bp. Basically, your implementation of context_plant_breakpoint() decides how to plant "Auto" breakpoint by either planting it or returning ERR_UNSUPPORTED.

Regards,
Eugene

-----Original Message-----
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Samuel Ghinet
Sent: Wednesday, October 07, 2015 7:30 AM
To: tcf-dev@xxxxxxxxxxx
Subject: [tcf-dev] breakpoints / access types

Hello,

I am working on a debugger using tcf and I've hit into an issue
concerning it & Eclipse, and I don't know what to make of it.

On debugging an application, when I toggle a breakpoint from Eclipse,
the tcf agent finds it to have the type "Auto".
However, looking at the function get_bp_access_types from breakpoints.c,
we see this:

 > if (virtual_addr && type != NULL && strcmp(type, "Software") == 0)
access_types |= CTX_BP_ACCESS_SOFTWARE;

Basically, if the breakpoint type is Auto (default case from Eclipse),
then the CTX_BP_ACCESS_SOFTWARE flag is not set, which means that when
the context_plant_breakpoint function is called, the debugger can only
assume that the user (here, Eclipse) had asked for a hardware breakpoint
- even though the "hardware" value of the BreakInstruction struct is 0.

So my question is, what is the expected behavior in tcf? Should "Auto"
be translated to "Software" or to "Hardware"? Or, there is a point where
the debugger (outside of tcf) is supposed to decide what "Auto" should mean?

Thanks,
Samuel Ghinet
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://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.