Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: wever on September 10, 2014, 04:13:07 pm
-
This happened at least 20x. Version 13.12 After SIGSEGV error, if and only if I click left from the yellow tooltip program Crashes. If I do not click left to make it disappear so it does not crash. I am always sending the data after crash, I have no idea if it has some sense or no. If you don't read the data so I won't send them.
-
Which tooltip do you mean ?
There are several.
-
...if and only if I click left from the yellow tooltip program Crashes. ....
"yellow tooltip"? I guess it is from CodeCompletion plugin, so the first step is try to "disable this plugin", and see this issue happens again.
The next step could be: show us some code and steps to reproduce this bug.
-
Here is image:
bottom right
(http://oi62.tinypic.com/348g8q0.jpg)
Actually I am not sure if I click on left or on the tooltip, but I think I clicked on the left, on the black screen area.
Yet notice: now it did not crash, but I clicked on left and on the tooltip. It crashed before many times when I recieved the signal and it was in the moment when some char * variable was not initiated but I tried to save data to the variable of that type.
-
Nope it is your program that crashes, not Code::Blocks... aren't you using the debugger to find just where :)
-
Ok, but why it crashes code::blocks? I am using debuger and I know where my program crashes. But should not the code::blocks prevent from self-crashing when it finds the problematic command?
-
Why do you think C::B has crashed?
I can see that C::B is in perfect health and alive on your screen shot...
-
Then I'll have to make screenshot when the C::B crashed.
-
Then I'll have to make screenshot when the C::B crashed.
I suggest looking up what doing undefined operations in C/C++ can result in happening!
PEBKAC
Tim S.
-
Sometimes I run into problems where the GDB debugger hangs and I have to kill the process in Task Manager before I can fully use CodeBlocks again, but I only have the IDE crash on me very rarely.