question about debugging arch. on netbeans

[Brad Walker <bw...@musings.com>]

I use NetBeans in my professional work and really enjoy it. Mostly I'm on
the C/C++ side of things. Occasionally, I do work in Java. Anyways, I have
a question about how the Netbeans architecture is set up for debugging C
applications.

Let's say I create a HelloWorld project and it contains just HelloWorld.c.
Then I start the app using the "Debug Project" option. Now, I can set
breakpoints and step over source code using the IDE.

I believe that under the covers this work is handled by Netbeans using gdb
to start my application. The IDE then keeps track internally by talking to
gdb.

So my question is in what modules does this magic happen? Is there an
overall arch. document someone can share with me?

Hopefully, my questions aren't confusing and thanks for any insight you can
provide.

-brad w.

Re: question about debugging arch. on netbeans

Hi

GDB is packaged in a module called cnd.debugger.gdb2. I don't think this module is in incubator-netbeans on github in case you are looking there. If I am not wrong this is part of third donation along with rest of the c/cpp modules.

Here are c/c++ debugging related modules. 

cnd.debugger.common2
cnd.debugger.dbx
cnd.debugger.gdb2

I suspect above modules use debugger api and spi
spi.debugger.ui
api.debugger

I haven't actually looked into any of these modules, so chances are I may be completely off. The prescription is to take the above with ATLEAST a bucket of salt.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists