Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Batch build problems (hangs/stalls if log window is not active)
oBFusCATed:
But I guess, I've posted on the wrong ticket... I thought this is the crash-on-exit issue.
Sorry...
Miguel Gimenez:
@obfuscated, the crash issue was indeed at the beginning of this thread, later moved to ticket 738. I have tested your patch, and the crash is gone. No apparent side effects neither in batch mode nor in GUI mode (Windows 7).
BlueHazzard:
To come back to this, because the stall hits me at the moment...
the patch obfuscated posted here in
--- Quote from: oBFusCATed on October 13, 2018, 11:42:13 am ---Can you try this patch (remove the old one):
--- Code: ---diff --git a/src/src/main.cpp b/src/src/main.cpp
index 886eead0f..7d4b74cc6 100644
--- a/src/src/main.cpp
+++ b/src/src/main.cpp
@@ -2720,7 +2720,6 @@ void MainFrame::OnApplicationClose(wxCloseEvent& event)
CodeBlocksEvent evt(cbEVT_APP_START_SHUTDOWN);
Manager::Get()->ProcessEvent(evt);
- Manager::Yield();
m_InitiatedShutdown = true;
Manager::BlockYields(true);
--- End code ---
The other patch just works around the problem. This one tries to fix it.
--- End quote ---
is not for the stalling but for a crash? Am i right?
The stalling is still a problem also with this patch?
[Edit:] i also created a ticket about the stall: https://sourceforge.net/p/codeblocks/tickets/854/
BlueHazzard:
@simons
If you are still here: Can you give some example how you use codeblocks with Jenkins? Some minimal configuration file and some use cases?
Thank you!
simons:
@BlueHazzard: Yes, still here. Thank's for opening a ticket. The patch from @oBFusCATed did not solve the stall problem for me, but your patch posted before that did (test_FixCompilingIdleHanging_use_PipedProcessLaunch_1.patch). I've running a patched version of CodeBlocks for a few months now on my server.
About my Jenkins setup: I run codeblocks from within a Jenkins pipeline through a batch file.
The pipeline looks something like this:
--- Code: ---...
stage('Build'){
steps {
bat "run_codeblocks.bat my_cb_workspace.workspace --build --target=release"
}
}
...
--- End code ---
and the batch file 'run_codeblocks.bat' runs CodeBlocks like this:
--- Code: ---...
codeblocks.exe" --no-check-associations --no-dde --no-splash-screen %*
...
--- End code ---
One could probably just run CodeBlocks directly from the 'bat'-step in the pipeline. However, we do some extra steps in the batch file to work-around some Visual Studio specific issues (like mspdbsrv.exe being killed by Jenkins when building debug targets).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version