[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Additional Info & Questions
|
Donny,
You're right that the C/C++ debug model is geared towards C/C++, but
there's a number of reasons for using it as the basis for the PTP
debug model:
- There have been discussions about unifying the platform and C/C++
(and Java) debug models into a single model.
- PTP language support will be initially targeted at C/C++ and
Fortran, and the Fortran language support will most likely use a
modified C/C++ debug model.
- The only alternative would be the Java model, and this is not going
to help with debugging parallel programs written in C/C++ and Fortran.
Having said that, I suspect that parallel debug support will probably
need to start at the platform level and filter down through C/C++ and
CDI.
Greg
On May 12, 2005, at 10:36 PM, Donny Kurniawan wrote:
Hello,
Additional info that I found:
- A result of stack tracing the stepOver() calls (see the attached
PDF)
- CThread (A thread in a C/C++ debug model) has a private variable of
the type ICDIThread. Thus, CThread is a proxy to the underlying CDI
thread.
CDI
- CDI is C/C++ Debug Interface (not Common Debug Interface).
It has C/C++ flavor in it, e.g. registers.
- Is PTP geared towards C/C++ ? What happened if we want to run
parallel Java programs?
org.eclipse.ptp.debug.core certainly depends on CDT plugins.
- The CDI (in CDI folder of org.eclipse.cdt.debug.core) doesn't depend
on the rest of CDT, so it can always be re-factored / forked to be put
into PTP.
Comments? Opinions?
Donny
<StepOver.pdf>
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
