Code::Blocks Forums
User forums => Help => Topic started by: ironhead on July 22, 2008, 01:19:56 pm
-
I'm having an issue with intermittent crashes with C::B. I've attached the RPT file, but it doesn't look like much help. I'm running Windows XP Pro using C::B and wxWidgets 2.8.8 compiled by myself using MinGW gcc/g++ 3.4.5.
If there is anything more you would like me to do, please let me know.
[attachment deleted by admin]
-
There are two crash reason:
1.) The first class of crashes come from the HexEditor plugin... so just disable/remove the HexEditor plugin if you don't need it. But I also believe this crash was fixed recently in SVN. So an update to a more recent nicghtly might work, too
2.) The second one is more difficult. I experience the same from time to time and it goes to:
wxProcess::IsInputAvailable (which wxWidgets)
from:
PipedProcess::HasInput (which is C::B)
and happens on "massive" compiler output parsing.
We are aware of this (Yiannis - remember our chat recently?!) but this is really hard to track down. For now you could try to disable/remove the CodeCompletion plugin (but that's probably not the cause) to get rid of this until we find the reason for this and thus a fix.
With regards, Morten.
-
There are two crash reason:
1.) The first class of crashes come from the HexEditor plugin... so just disable/remove the HexEditor plugin if you don't need it. But I also believe this crash was fixed recently in SVN. So an update to a more recent nicghtly might work, too
Indeed, it seems that using the arrow keys in HexEditor is now causing a crash (using SVN 5154) I've reported it on the HexEditor plugin thread, so hopefully byo can take a look at that.
2.) The second one is more difficult. I experience the same from time to time and it goes to:
wxProcess::IsInputAvailable (which wxWidgets)
from:
PipedProcess::HasInput (which is C::B)
and happens on "massive" compiler output parsing.
We are aware of this (Yiannis - remember our chat recently?!) but this is really hard to track down. For now you could try to disable/remove the CodeCompletion plugin (but that's probably not the cause) to get rid of this until we find the reason for this and thus a fix.
I'll keep tabs on when I see this occur, and if there is any predictability in terms of reproducing the error, I will let you know.
Thanx!
Chris
-
2.) The second one is more difficult. I experience the same from time to time and it goes to:
wxProcess::IsInputAvailable (which wxWidgets)
from:
PipedProcess::HasInput (which is C::B)
and happens on "massive" compiler output parsing.
We are aware of this (Yiannis - remember our chat recently?!) but this is really hard to track down. For now you could try to disable/remove the CodeCompletion plugin (but that's probably not the cause) to get rid of this until we find the reason for this and thus a fix.
I'm systematically observe this crash removing one lib from the linking option. This force a long list of messages in the build log, at linking time, that triggers the crash.
So I cannot forget a lib.. or crash is assured :D
Max
-
I'm not sure if it's related, but it looks like there were issues in earlier versions of wxWidgets on Mac that crashed when calling IsInputAvailable. Could this actually be a bug in wxWidgets?
-
I'm not sure if it's related, but it looks like there were issues in earlier versions of wxWidgets on Mac that crashed when calling IsInputAvailable. Could this actually be a bug in wxWidgets?
Interesting! Can you provide references? Cause in fact we have (rare) crashes pointing to this Method on Windows, too.