User forums > Using Code::Blocks

Debug in a separate window?

(1/5) > >>

Keeper:
I have an application that uses a shared library.  I am debugging this shared library.  When I debug the library in C::B, it works fine except I have no access to the base program to send it commands and change options.

Is there any way to launch the debug process in a separate terminal window when everything is handled through bash and GDB?  In other words, how do I run the base application as a console application?  Since it is being run from GDB?

C::B 8.02
Linux Mint 7/Ubuntu 9.04 (Gnome)

Thanks,
Keeper

EDIT:  Other than attaching to it after I run it via a script?

oBFusCATed:
Do you have the source of the host application and do you have a C::B project for it?
If you have, you could make a workspace that contains the application and the library.
Then you could debug the application and set breakpoints in the library code (I think).

Keeper:
No, the source application is a private app.  I'm writing a plugin for it, so I have the SDK, but not the full blown code.

Jenna:
It should work, if you set it as host application in "Project -> Set programs arguments..." .

Keeper:
The debugging works, but I have no interaction with the main program.  That's the problem.  KDevelop offers me a checkmark to debug in a separate window.  Didn't known if C::B had the same sort of option or workaround.

Navigation

[0] Message Index

[#] Next page