Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Crashes anyone??

<< < (3/6) > >>

MortenMacFly:

--- Quote from: daniloz on December 07, 2010, 01:48:49 pm ---Here is the RPT file:

--- End quote ---
I think generally the report files are of no help if you don't have the related compiled version of C::B that includes the debugging symbols. If you do so, you can try to apply this tool:

http://forums.codeblocks.org/index.php/topic,13129.msg88254.html#msg88254

...and report the de-mangeled output here. Than we can really trace to the root of the crashes. From the log I'd say it's ThreadSearch and CC.

daniloz:
Thanks for the reply Morten... I've just edited my post and included some more information (file name and lines) for the ThreadSearch and CC plugins...

Interesting is that I was working on another software and C::B was just running in the background when the crash occurred....

Btw, I'm using wxWidgets 2.8.11. Could it be the cause?

Jenna:
The ThreadSearchEvent is timer-driven, so it can occur without user-action, the classbrowser event is (most likely) a selection-change event in classbrowser (I'm not absolutely sure, because you either have different sources, or the debugger spits out incorrect line-numbers, maybe due to conditional compiling).

Are you absolutely sure, your sources and your object directory have been really clean, before building C::B ?
No devel-, output- and .objs-subdirectory no include/*.gch ?

Did you try it with wx2.8.11 ?
There have been some changes between 10 and 11, if I remember correctly.

MortenMacFly:

--- Quote from: daniloz on December 07, 2010, 02:11:13 pm ---Thanks for the reply Morten... I've just edited my post and included some more information (file name and lines) for the ThreadSearch and CC plugins...

--- End quote ---
Good to see, however, where I am currently I don't access to my sources... ;-)

However...

--- Quote from: daniloz on December 07, 2010, 02:11:13 pm ---Btw, I'm using wxWidgets 2.8.11. Could it be the cause?

--- End quote ---
...this could indeed be a reason. Several users have reported issues (a.k.a. crashes) with his version of wxWidgets. There were some patches in the forums addressing these, so if you don't have them applied you should try these. BTW: If I remember Correctly, then this was actually a wx error. Any chance you try 2.8.10?

Loaden:
Please trying rev6877, and feedback?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version