News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Not seeing the output terminal while debugging a shared library

Started by edwin, September 02, 2010, 07:30:33 PM

Previous topic - Next topic

edwin


Hello C::B team,

I have a quick debugging question. I searched the support forum for the answer but failed. Forgive me if this question has already been answered.


Overview:
1)
I am debugging a shared library on Ubuntu Linux (10.04) using CodeBlocks SVN 6564.

2)
I use a native executable "driver program" to perform testing of the shared library.

3)
I have configured the shared library to use the "driver program" as its executable using

Project->Set program's arguments

Where I specify the path to the executable.

4)
Debugging the shared library works fine but I am not seeing an output terminal where the "driver program" uses printf() to display test results.

I am still looking for the solution. If someone can assist, that would be terrific.


Thank you everyone,

edwin


oBFusCATed

This feature is implemented in the debuggers branch.
There you can check "Project -> Set program's arguments -> Run host in terminal" and you get a terminal when debugging the lib.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

edwin

Thanks oBFusCATed,


Than sounds very good.  :)


1)
Is the "debugger" branch:

svn://svn.berlios.de/codeblocks/branches/wxpropgrid_debugger


2)
Will it be OK to continue my development using the debugger branch HEAD instead of trunk SVN 6564?

TIA,

edwin



MortenMacFly

Quote from: edwin on September 02, 2010, 08:52:46 PM
Will it be OK to continue my development using the debugger branch HEAD instead of trunk SVN 6564?
No objections from my point of view, but please sync yourself with oBFusCATed when it comes to patches for the branch. Probably oBFusCATed can apply them to his version and send me a patch accordingly. I just want to avoid that I do the merge... ;-)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

oBFusCATed

Morten: I think, he is asking if the debugger's branch is usable from the user's point of view :)

edwin: the branch should be usable, also it is mostly synced with trunk, so you won't miss any feature from the nightly.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

edwin

Thank you both for your answers. 

MortenMacFly:
Yes – I understand. Very good point.

oBFusCATed:
Yes you are correct. I was asking about usability from the "users" perspective. I see the differences in the trunk vs. the debugger branch. Very good.

BTW, the debugger branch is this:

svn://svn.berlios.de/codeblocks/branches/wxpropgrid_debugger

correct?


Thank you guys,

edwin


oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]