Hi all,
I would like to
specify some more of my point in the previous mail. In the “CBreakpointManager”
class, there is a function “setBreakpointsOnTarget0()”. In the
function, it is observed that it tries to get the appropriate implementation of
the ICDITarget. (i.e ICDITarget cdiTarget = getCDITarget(); ).
I would like to know the
possibility of writing own implementation of ‘ICDITarget’ and
register with the platform.
My understanding is that the class ‘Target’
is one such implementation. My intention is to use my own implementation of the
setWatchpoint() method so that I can implement custom watch point type. Can
anybody please advise me whether this approach is right. Please help.
Thanks
Sudeep
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf
Of Sudeep R. K.
Sent: Wednesday, September 23, 2009 8:11 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] CDT 6.0: Supporting Data watch point without
patchingCBreakpointManager
Hi all,
We have been trying to implement the data watch point
support in CDT 6.0 based platform.
On analyzing, it is understood that we may need to patch
‘CBreakpointManager’
( “org.eclipse.cdt.debug.internal.core”) and
some other places. Is there any alternative by which
We can avoid patching the ‘CBreakpointManager’.
Pls help
Thanks
Sudeep
*****
Confidentiality Statement/Disclaimer *****
This message and any attachments is intended for the sole use of the intended
recipient. It may contain confidential information. Any unauthorized use,
dissemination or modification is strictly prohibited. If you are not the
intended recipient, please notify the sender immediately then delete it from
all your systems, and do not copy, use or print. Internet communications are
not secure and it is the responsibility of the recipient to make sure that it
is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or
modifications made to the contents. If you require any form of confirmation of
the contents, please contact the company/sender. The company/sender is not
liable for any errors or omissions in the content of this message.
***** Confidentiality Statement/Disclaimer *****