Author Topic: Debugging cursor disappearing  (Read 10651 times)

Offline Léa Massiot

  • Multiple posting newcomer
  • *
  • Posts: 39
Re: Debugging cursor disappearing
« Reply #15 on: November 13, 2011, 01:33:23 pm »
Quote from: oBFusCATed
/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

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11938
    • Travis build status
Re: Debugging cursor disappearing
« Reply #16 on: November 13, 2011, 01:58:56 pm »
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"
(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!]

Offline Léa Massiot

  • Multiple posting newcomer
  • *
  • Posts: 39
Re: Debugging cursor disappearing
« Reply #17 on: November 13, 2011, 02:35:06 pm »
@oBFusCATed : Thank you very much for answering my questions.

Quote from: 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.
Ok. Thank you for explaining.

Quote from: oBFusCATed
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...

Quote from: oBFusCATed
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: [Select]
"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
« Last Edit: November 13, 2011, 02:42:04 pm by Léa Massiot »

Offline Léa Massiot

  • Multiple posting newcomer
  • *
  • Posts: 39
Re: Debugging cursor disappearing
« Reply #18 on: November 13, 2011, 10:33:35 pm »
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

Offline Léa Massiot

  • Multiple posting newcomer
  • *
  • Posts: 39
Re: Debugging cursor disappearing
« Reply #19 on: November 13, 2011, 11:19:47 pm »
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: [Select]
> apt-get remove codeblocks codeblocks-contrib
> apt-get update
> apt-get install codeblocks codeblocks-contrib
Best regards,
--
Léa

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11938
    • Travis build status
Re: Debugging cursor disappearing
« Reply #20 on: November 14, 2011, 12:16:32 am »
The normal way you upgrade your debian system. Read their help/manual.
(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!]

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7265
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: Debugging cursor disappearing
« Reply #21 on: November 14, 2011, 04:56:28 am »
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: [Select]
> 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).

Offline Léa Massiot

  • Multiple posting newcomer
  • *
  • Posts: 39
Re: Debugging cursor disappearing
« Reply #22 on: November 14, 2011, 01:15:18 pm »
@oBFusCATed and @Jens : Thank you for your answers.

Quote from: oBFusCATed
The normal way you upgrade your debian system. Read their help/manual.
I read something like:
Code: [Select]
> apt-get install codeblocks codeblocks-contribwould upgade the packages... (if they are already installed which is my case).
@Jens : Do you confirm?

Again, about:
Code: [Select]
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

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11938
    • Travis build status
Re: Debugging cursor disappearing
« Reply #23 on: November 14, 2011, 02:07:48 pm »
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.
(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!]