Debugging cursor disappearing

[Léa Massiot]

/usr/lib/libstdc++.so.6 is shared library and there is no source for it...

I'm sorry but I do not understand what is so obvious in your answer...

If it's not too much asking, could you answer "Question 1" and "Question 2" in my previous post?

Could you try to explain why the fact that "libstdc++.so.6 is a shared library and there is no source for it" can explain such a behaviour...? I mean, what is this message: "Unknown file: /usr/lib/libstdc++.so.6"? This file exists!

Please forgive me if I'm missing an obvious point!
Thanks and regards!
--
Léa

[oBFusCATed]

If there is no source, the file could not be opened in C::B. C::B is telling you that it doesn't know the type of the life => it is not a source file and thus it cannot open it in the editor.

Q1: No, if inside the function you catch it
Q2: The stdout/stderr of your program is printed to a terminal on linux/macosx and to cmd.exe on windows. This works only if the target type is "console"

[Léa Massiot]

@oBFusCATed : Thank you very much for answering my questions.

If there is no source, the file could not be opened in C::B. C::B is telling you that it doesn't know the type of the life => it is not a source file and thus it cannot open it in the editor.

Ok. Thank you for explaining.

Q1: No, if inside the function you catch it

- Well, I've added a bp in front of 'std::cout << "Something went wrong."' inside the "catch(...)" block
=> but this bp is NEVER reached...
- I've also added a bp in front of 'std::cout << "END OF aMethod()"' after the try/catch block at the end of the method
=> and this bp IS reached...

=> So an exception is thrown but is not caught!
Really I'm confused (maybe I shouldn't be). I guess I'm missing something...

Q2: The stdout/stderr of your program is printed to a terminal on linux/macosx and to cmd.exe on windows. This works only if the target type is "console"

Ok. So, to have the console pop up, here is what I did:

Code

"Project -> Properties -> Build targets -> Debug" 
"Type: Console application"
I checked "Pause when execution ends".
(If this check box is unchecked, no console actually pops up).

Best regards,
--
Léa

[Léa Massiot]

Hello again,
Apart from the fact that I do not really understand that exception being thrown and not caught or whatever, it's now working properly with the settings you suggested. So thank you very much for your help.
Best regards,
--
Léa

[Léa Massiot]

Again. Sorry. A few last questions:

1) Why did you ask me to install a nightly build? To benefit from the latest functionalities?
How different is a nightly build from the sources I downloaded and installed at first? (Actually, this one is better, for example it's really nice to be able to double-click to get the view full-window!)

2) If I want to get the next nightly build, how can I do that? Like this?

Code

> apt-get remove codeblocks codeblocks-contrib
> apt-get update
> apt-get install codeblocks codeblocks-contrib

Best regards,
--
Léa

[oBFusCATed]

The normal way you upgrade your debian system. Read their help/manual.

[Jenna]

Again. Sorry. A few last questions:

1) Why did you ask me to install a nightly build? To benefit from the latest functionalities?
How different is a nightly build from the sources I downloaded and installed at first? (Actually, this one is better, for example it's really nice to be able to double-click to get the view full-window!)

2) If I want to get the next nightly build, how can I do that? Like this?

Code

> apt-get remove codeblocks codeblocks-contrib
> apt-get update
> apt-get install codeblocks codeblocks-contrib

Best regards,
--
Léa

If you have the 10.05 release installed, you should uninstall it, otherwise apt will not see the newer packages as far as I know.
You might have to uninstall the *-common-packages also.

If you already have a nightly and use my repo, it should work flawlessly.

I suggest using a package-manager like synaptic to uninstall/install C::B (and other software).

[Léa Massiot]

@oBFusCATed and @Jens : Thank you for your answers.

The normal way you upgrade your debian system. Read their help/manual.

I read something like:

Code

> apt-get install codeblocks codeblocks-contrib

would upgade the packages... (if they are already installed which is my case).
@Jens : Do you confirm?

Again, about:

Code

Unknown file: /usr/lib/libstdc++.so.6
In __cxa_throw () (/usr/lib/libstdc++.so.6)

Does it really mean an exception is being thrown?
I don't know if I should investigate further...
Literature about "__cxa_throw" on the Web is rather esoteric to me...

Thanks for your expertise.
--
Léa

[oBFusCATed]

Yes, it is. You can add initial command "catch catch" to see where the catch happens.
I've not tried this command, but I guess this is what it does.