Code::Blocks Forums
User forums => Using Code::Blocks => Topic started by: Keeper on December 29, 2009, 10:52:14 pm
-
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?
-
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).
-
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.
-
It should work, if you set it as host application in "Project -> Set programs arguments..." .
-
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.
-
I'm not sure what you mean.
If you are able to debug and set breakpoints the interaction with the main app should work as if you do not run it through the debugger.
If I create a C::B plugin, I can link it again and run it through a stripped version of C::B (no debugging symbols). I can interact with the main app (C::B in this case) as if I debug the plugin with the C::B sources available.
-
Ok, let me clear it up a bit :D
Say you open a terminal, and change directories to where the executable is.
I run this executable and it runs in that same terminal window. It doesn't open a new window, it's a text/console application.
So when you run it via the debugger, it only shows up if I turn on debugging log. Even then it doesn't show everything. In order to run debugging from C::B, I would need to somehow tell GDB ( I guess ) to start this up in another window. Or C::B could open the console and bash all the commands via that and then the program would start in that window instead of "behind the scenes" in C::B.
-
jens: he wants the host app to be run inside terminal, I think.
C::B should be modified to support this feature. I'll add it in my TODO for the debugger branch.
-
jens: he wants the host app to be run inside terminal, I think.
Why is it I can never seem to express exactly what I want?!??!?!?! Yes, that is exactly what I was trying to say. :D
-
jens: he wants the host app to be run inside terminal, I think.
Why is it I can never seem to express exactly what I want?!??!?!?! Yes, that is exactly what I was trying to say. :D
I understood after your answer to my previous post.
What you can try, is to start the app in a console, get the pid with ps and attach the debugger via "Debug -> Attach to process".
I never did this, so I don't know how usable it is.
-
You can attach to the process once it's running. But if you want to debug the program as it loads, you are out of luck. Any news as to when this will be added to the debugging features?
TIA,
Keeper
-
What a coincidence, I started work on this feature yesterday :)
-
This is great news!!! Thank you :D
-
I've been out of the linux dev side for a while ... I have downloaded the latest from the SVN. I didn't see where I can set this type of debugging up. Is this implemented yet?
-
Yes it is, but you'll have to use the debuggers branch... http://svn.berlios.de/wsvn/codeblocks/branches/wxpropgrid_debugger/?rev=6463&peg=6463#ab1bb068457ecc925a5b07fe41a91d401
-
I'm getting this:
warning: GDB: Failed to set controlling terminal: Operation not permitted
Also, is it possible to set the path to the executable? it needs to be run from a different directory than the codebase. I have tried several things, but I seem to be missing it.
Thanks!
Keeper
-
1. The warning is emitted by gdb and it is not a problem.
2. You can set the working directory in Project -> Properties -> Build options -> Working dir or something like that.
-
Well, I tried to run GDB just on it's own outside of codeblocks and it seems it doesn't work. I get the "Cannot find new threads: generic error" error.
Oh well.
Thanks for the help!
-
This seems like a very popular gdb problem, use your favorite search engine to find solutions for it.
-
Well I tried just GDB on my lenny distro and it worked. Must be some kind of issue with the newest Ubuntu.
I'm going to reload my lenny and see if I can get it to work there.
-
Ok, after many problems with Ubuntu. I finally reloaded Debian. Of course, my hard drive went out, and then I couldn't get the "debuggers branch" to compile on lenny. I figured out the issues and got it compiled.
Worked like a charm. Cheers!
Will this make it to the main distro?
-
Will this make it to the main distro?
Of C::B? Yes it will, someday, but first it needs some testing...
-
Sounds good! I'm going to use it/test it all the time ... I'll post back here if I see any issues.
-
Please post in http://forums.codeblocks.org/index.php/topic,10908.0.html if you find problems...