User forums > Help
Tools Menu item causing wxWidgets Debug alert in C::B
cacb:
Hi, I am using Code::Blocks nightly build svn 11628 under Windows 10 and Windows 7 and seeing this issue in both places.
I use git for source control and find it convenient to add a "Git Gui Here" item in the basic Tools menu of Code::Blocks. However, when I use this option I am almost always (not 100% of the time though) met with a "wxWidgets Debug Alert" 'threatening' to crash the IDE unless I ask it not to. When I reply 'No' it all works as expected, the git gui appears.
Btw. I use the same basic git gui on linux as well, with no issues.
So the question is: What is causing this, and is there anything I can do to prevent it from happening under Windows?
oBFusCATed:
Someone with a windows build should spend some time to see why this happens.
From the docs a possible cause is incorrect return value by git.exe.
Can you switch to "Launch the tool visible detached" and report if it fixes the problem?
cacb:
--- Quote from: oBFusCATed on May 06, 2019, 10:53:41 am ---Someone with a windows build should spend some time to see why this happens.
From the docs a possible cause is incorrect return value by git.exe.
Can you switch to "Launch the tool visible detached" and report if it fixes the problem?
--- End quote ---
I tried "Launch the tool visible detached", but then I just get an unwanted terminal, plus the same Debug Alert window, so it does not fix it. I also tried the other options without success.
It sounds possible that this is something caused by git.exe, since I use the same technique for other things without the same kind of issue. However, git is the most used tool so it would be nice if it worked with git.
oBFusCATed:
Yes, but from MS' docs (https://docs.microsoft.com/en-us/windows/desktop/api/processthreadsapi/nf-processthreadsapi-getexitcodeprocess):
--- Quote ---Important The GetExitCodeProcess function returns a valid error code defined by the application only after the thread terminates. Therefore, an application should not use STILL_ACTIVE (259) as an error code. If a thread returns STILL_ACTIVE (259) as an error code, applications that test for this value could interpret it to mean that the thread is still running and continue to test for the completion of the thread after the thread has terminated, which could put the application into an infinite loop.
--- End quote ---
oBFusCATed:
BTW: This assert is added to wxWidgets 12 ago https://github.com/wxWidgets/wxWidgets/blame/master/src/msw/utilsexc.cpp#L308
Navigation
[0] Message Index
[#] Next page
Go to full version