Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Re: Interaction between perspectives.


Do you display the stack frames for Java and C/C++ code under the same
thread? And is there a need to introduce additional perspectives? The
idea of the Debug perspective in Eclipse is to host all debug sessions
regardless of the type and language.
By the way, as far as I know you are using the Harmony JVM as a backend
debugger for Java, what is your backend for C/C++?

Mikhail Khodjaiants
ARM Ltd.
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Vitaly Provodin
Sent: 23 October 2006 10:28
To: CDT General developers list.
Subject: Re: [cdt-dev] Re: Interaction between perspectives.


We are working on the mixed Java/JNI debugger supporting currently Java
and C/C++ languages. It is being integrated into Eclipse IDE under the
Debug perspective. Currently, we are able to set and stop on line
breakpoints in both Java and C/C++ code. Depending on what stack frame
is active, we are able to watch Java and native data - variables, their
values. It works in the ordinary debug perspective.
Probably, (two or more) separate percpectives for each debug-info
representation might be introduced, but at this moment there are no
well-defined vision of this.

Vitaly Provodin,
Intel Middleware Products Division

On 10/18/06, Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx> wrote:
> Ramesh -
> many thanks for your request. There are some initiatives in the area 
> of debugger inter-communications, but none is really mature yet.
> One problem is that when an event in debugger A should initiate some 
> action in debugger B, you'd typically want to do this with very low 
> latency. Which requires a solution sitting "very close to the target",

> which typically means vendor-specific non-standard (read: non-eclipse)

> solutions.
> If low latency this is not a requirement, some Eclipse UI based event 
> handling could be the right solution. We thought that the Target 
> Management Project might be the Umbrella defining such events, to be 
> understood by many debuggers that want to communicate. An empty 
> discussion page is available under "Inter-Debugger Communications" 
> from
> I'm not sure how far the Device Debugging Project has already 
> progressed to support inter-debugger communications.
> Another initiative I know of, is a Java/JNI/gdb debugger integration 
> being investigated by intel. You might be able to meet these folks on 
> the CDT groups.
> I'm copying the dsdp-tm-dev, dsdp-dd-dev and cdt-dev mailing lists 
> with this answer. If there is any developer that can help you further,

> please chime in.
> Thanks
> Martin
> Ramesh Ramaiyer schrieb:
> > Hi all,
> > We are working on a SoC with three distinct cores. Each of these 
> > cores have their own debuggers. Very soon they live under Eclipse. 
> > The expectation from developers is that they should be able to debug

> > the interactions between these cores as well.
> >
> > This implies that interaction between Perspectives should be
> > Under the current implementation each debugger has its own
> >  An example usecase might be - when a break point is hit on one 
> > core, the other two stopping (ASAP). Another might be the ability to

> > place breakpoints on programs running on any of the cores.
> >
> > In my mind these usecases are similar to, some one stepping through 
> > a piece of java code which makes a JNI call. If the JNI is written 
> > in C++, is it possible to automatically invoke C++ perspective and
switch to that?
> >
> > I don't know if such a support is already present. Can you point me 
> > in the right direction please?
> >
> > Any help is greatly appreciated.
> > Thanks and regards
> > Ramesh
> > Note: I have also placed this question on Eclipse Newcomer group.
> --
> Martin Oberhuber
> Wind River Systems, Inc.
> Target Management Project Lead, DSDP PMC Member 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
cdt-dev mailing list

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.

Back to the top