Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-debug-dev] RE: [cdt-dev] Windows Debug API - CDI Implementation

It's a bit of chicken and egg, no? First we need to build the debugger. 
Right now, printf is my friend. Once we have the debugger in place, we 
should be able attach to a running Java VM and debug any native libraries. 
Once we get that far, we can look at tighter integration between the Java 
debuggers (i.e. JVMDI and friends) and our CDT debuggers.

One thing I have found, it is pretty handy having a good development 
environment for writing native libraries when building apps based on 
Eclipse. Java is great, for certain things...

Doug Schaefer, IBM's Eclipse CDT Architect
Ottawa (Palladium), Ontario, Canada



"Recoskie, Chris" <crecoskie@xxxxxx> 
Sent by: cdt-debug-dev-admin@xxxxxxxxxxx
05/22/2004 09:52 AM
Please respond to
cdt-debug-dev


To
<cdt-dev@xxxxxxxxxxx>, <cdt-debug-dev@xxxxxxxxxxx>
cc

Subject
[cdt-debug-dev] RE: [cdt-dev] Windows Debug API - CDI Implementation






+1 from me

Question:  What exactly is your setup of mixing C/C++ and Java and
debugging them both?

I'm guessing that the reason you're cooking this up is that you have a
Java project which is using JNI and you want to debug the calls into the
native code...

> -----Original Message-----
> From: cdt-dev-admin@xxxxxxxxxxx 
> [mailto:cdt-dev-admin@xxxxxxxxxxx] On Behalf Of Douglas Schaefer
> Sent: Friday, May 21, 2004 2:39 PM
> To: cdt-debug-dev@xxxxxxxxxxx; cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] Windows Debug API - CDI Implementation
> 
> 
> Hey gang,
> 
> I have been playing around with some mixed mode JDT/CDT 
> projects and have 
> put together an implementation of the CDI that calls into the Windows 
> Debug APIs. This became interesting when Microsoft released their 
> optimizing compiler as a free download. The CDT would be a 
> great place for 
> people wanting to use that compiler with Microsoft's free 
> SDKs and would 
> like an IDE for it. Currently, I have support for creating a process, 
> inserting breakpoints, and showing the stack and variables at 
> breakpoints. 
> A lot of work still needs to be done to correctly interpret 
> the variables 
> amongst other things. And I'm sure there are things I'm doing wrong.
> 
> We have talked a little about this in the past so I know 
> there is interest 
> in this. I'd like to contribute my work to the CDT as a 
> starting point for 
> this integration. I'm doing this in the background so any 
> help would be 
> greatly appreciated. I am also hoping that by providing 
> better support for 
> Windows development, we can grow the CDT community a bit more in that 
> direction than we have in the past.
> 
> Thoughts? Go for its? Don't you dares?
> 
> Cheers,
> Doug Schaefer, IBM's Eclipse CDT Architect
> Ottawa (Palladium), Ontario, Canada 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/cdt-dev
> 
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev




Back to the top