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

Batch build problems (hangs/stalls if log window is not active)

<< < (4/7) > >>

BlueHazzard:

--- Quote from: simons on September 27, 2018, 09:28:11 am ---Has anyone been able to reproduce the problem using the "fake_gcc"? I pushed the new configuration to the repo. Any ideas on how to move on from here?

--- End quote ---
no, i was not able to reproduce it with your latest fake_gcc...

I have tried future with WinDBG and gcc and i got this information:
cc1plus.exe:

--- Code: ---DEFAULT_BUCKET_ID:  APPLICATION_HANG_BlockedOn_FileIO

PRIMARY_PROBLEM_CLASS:  BlockedOn_FileIO

THREAD_SHA1_HASH_MOD_FUNC:  c281b8792a9b0b7b09f56f4b37bca845ce1f1b92

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5428a93740841021c6fded59898de991617bd52a

LAST_CONTROL_TRANSFER:  from 7618e004 to 773af96d

STACK_TEXT: 
0028f340 7618e004 00000044 00000000 00000000 ntdll!NtWriteFile+0x15
0028f3a4 76ca12cc 00000044 0028f418 00000400 KERNELBASE!WriteFile+0x113
0028f3c0 76dd4236 00000044 0028f418 00000400 kernel32!WriteFileImplementation+0x76
0028f97c 76dd40eb 00000002 12b99598 00000877 msvcrt!_write_nolock+0x3fb
0028f9c0 76dcf15e 00000002 12b99598 00000877 msvcrt!_write+0x9f
0028f9e0 76dcf1a0 76e62940 00000000 0028fa28 msvcrt!_flush+0x3b
0028f9f0 76dd416d 76e62940 ff7a9eca 01024a9c msvcrt!_fflush_nolock+0x1c
0028fa28 00ea85fd 76e62940 0028fb18 0028fb18 msvcrt!fflush+0x30
WARNING: Stack unwind information not available. Following frames may be wrong.
0028faf8 00ea505e 01463500 0028fb18 00000034 cc1plus+0xaa85fd
0028fb48 00429b48 000001aa 01024a9c 15d3a2c0 cc1plus+0xaa505e
0028fb58 0043f039 15153910 00000000 01bc5540 cc1plus+0x29b48
0028fbb8 004cc7c0 00000001 00000001 00000000 cc1plus+0x3f039
0028fbd8 004cd4f1 1917b708 00465250 0c95bf80 cc1plus+0xcc7c0
0028fbf8 0043fd61 1917b708 00000000 016b9cc0 cc1plus+0xcd4f1
00000000 00000000 00000000 00000000 00000000 cc1plus+0x3fd61

--- End code ---

mingw32g++.exe:

--- Code: ---DERIVED_WAIT_CHAIN:    00 ca8.24c8 Process Handle

WAIT_CHAIN_COMMAND:  ~0s;k;;

THREAD_ATTRIBUTES:
BLOCKING_THREAD:  000024c8

DEFAULT_BUCKET_ID:  APPLICATION_HANG_BlockedOn_ProcessHandle

PRIMARY_PROBLEM_CLASS:  BlockedOn_ProcessHandle

THREAD_SHA1_HASH_MOD_FUNC:  e48a380cac1320f60a2487066e7609815690d73a

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  bcd69aa1f032d972611d5e1bfe1a686de0b4cd74

LAST_CONTROL_TRANSFER:  from 761915ce to 773af901

STACK_TEXT: 
0028f490 761915ce 00000054 00000000 00000000 ntdll!NtWaitForSingleObject+0x15
0028f4fc 76ca1194 00000054 ffffffff 00000000 KERNELBASE!WaitForSingleObjectEx+0x98
0028f514 76ca1148 00000054 ffffffff 00000000 kernel32!WaitForSingleObjectExImplementation+0x75
0028f528 0044c64b 00000054 ffffffff 0028f6a8 kernel32!WaitForSingleObject+0x12
WARNING: Stack unwind information not available. Following frames may be wrong.
0028f538 00444aa8 00000004 00360100 0036fe33 mingw32_g__+0x4c64b
0028f6a8 0040a4c5 0036c368 004f4220 0000002f mingw32_g__+0x44aa8
0028f738 0040ca8e 003688f9 004f4aa3 00000001 mingw32_g__+0xa4c5
0028f79c 773c3476 77981bc8 0047fe4a 004f4aa1 mingw32_g__+0xca8e
0028f938 00401577 004f3470 0047ff78 00000019 ntdll!RtlpAllocateHeap+0xe66
0028f958 0040a917 0047c9b4 00361c32 00000009 mingw32_g__+0x1577
0028f9e8 0040ca8e 003688f9 004f3fdb 0000000c mingw32_g__+0xa917
0028fa48 00406a05 773c3476 77981898 004f3bcd mingw32_g__+0xca8e
0028faf8 0040ca8e 003688f9 004f3d3b 00000002 mingw32_g__+0x6a05
0028fb5c 773c3476 77981f88 0047db8d 004f3d39 mingw32_g__+0xca8e
0028fc88 0040b295 00000002 00000002 773c4355 ntdll!RtlpAllocateHeap+0xe66
0028fd18 0040ca8e 003688f9 0047db8b 00000001 mingw32_g__+0xb295
0028fd74 773c3476 003c34a1 00000001 00000010 mingw32_g__+0xca8e
0028fe48 0040e0b0 00000000 00000000 004f1a58 ntdll!RtlpAllocateHeap+0xe66
0028fe78 0040e1d8 0047db48 00000001 0028ffc4 mingw32_g__+0xe0b0
0028ff18 004010fd 0028ff28 76dd9e34 fffde000 mingw32_g__+0xe1d8
0028ff94 773c9832 fffde000 77981c68 00000000 mingw32_g__+0x10fd
0028ffd4 773c9805 00401280 fffde000 00000000 ntdll!__RtlUserThreadStart+0x70
0028ffec 00000000 00401280 fffde000 00000000 ntdll!_RtlUserThreadStart+0x1b

--- End code ---

codeblocks.exe:

--- Code: ---DERIVED_WAIT_CHAIN:    00 26b8.1fbc Unknown

WAIT_CHAIN_COMMAND:  ~0s;k;;

THREAD_ATTRIBUTES:
BLOCKING_THREAD:  00001fbc

THREAD_SHA1_HASH_MOD_FUNC:  71431138aca2c5693a1cab1a8c383575c7f4d911

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ca61d71375c8d331e524a6f7a93b8a1e35ccd897

LAST_CONTROL_TRANSFER:  from 76ea790d to 76ea78d7

STACK_TEXT: 
0028eefc 76ea790d 0028f0b8 00000000 00000000 user32!NtUserGetMessage+0x15
0028ef18 0ca4dfd6 0028f0b8 00000000 00000000 user32!GetMessageW+0x33
WARNING: Stack unwind information not available. Following frames may be wrong.
0028ef38 0c24f8a3 0028f0b8 00000000 00000000 wxmsw30ud_gcc_custom!Z10GetMessageP6tagMSGP6HWND__jj+0x26
0028f048 0c35a7aa 0028f0b8 0028f138 0028f068 wxmsw30ud_gcc_custom!ZN18wxMSWEventLoopBase14GetNextMessageEP6tagMSG+0x77
0028f0f8 0c1947e9 00000000 0108fb44 0000032c wxmsw30ud_gcc_custom!ZN14wxGUIEventLoop8DispatchEv+0x52
0028f118 0c1948b1 0028f138 00001fbc 00000000 wxmsw30ud_gcc_custom!ZN17wxEventLoopManual13ProcessEventsEv+0x4d
0028f198 0c194503 0028f210 19e5925c 00000000 wxmsw30ud_gcc_custom!ZN17wxEventLoopManual5DoRunEv+0xc5
0028f238 0cac3ad3 00000024 0028f2cc 0028f258 wxmsw30ud_gcc_custom!ZN15wxEventLoopBase3RunEv+0x137
0028f258 0c354cf0 181a7ae4 19e59250 00000000 wxmsw30ud_gcc_custom!ZN17wxDialogModalData7RunLoopEv+0x13
0028f2f8 004074e1 17d86654 0028f548 0028f3a0 wxmsw30ud_gcc_custom!ZN8wxDialog9ShowModalEv+0x18e
0028f598 00405156 181421c0 19c9de70 00000000 codeblocks_exe+0x74e1
0028fd28 0053b982 00000000 0028fd6c 00000000 codeblocks_exe+0x5156
0028fd48 0c1d1453 00000008 17d5d9f0 00027eb4 codeblocks_exe+0x13b982
0028fdc8 0c290d0c 0ce0d340 17d5d9f0 0cb1c7c8 wxmsw30ud_gcc_custom!Z11wxEntryRealRiPPw+0xab
0028fde8 0c2912c4 0ce0d340 17d5d9f0 0cb1c7c8 wxmsw30ud_gcc_custom!Z7wxEntryRiPPw+0x18
0028fe78 00402471 00400000 00000000 00000000 wxmsw30ud_gcc_custom!Z7wxEntryP11HINSTANCE__S0_Pci+0xd8
0028fe98 005ee2bb 00400000 00000000 031a5680 codeblocks_exe+0x2471
0028ff18 004010fd 7efde000 00000000 7efde000 codeblocks_exe+0x1ee2bb
0028ff94 773c9832 7efde000 77988401 00000000 codeblocks_exe+0x10fd
0028ffd4 773c9805 004012a0 7efde000 00000000 ntdll!__RtlUserThreadStart+0x70
0028ffec 00000000 004012a0 7efde000 00000000 ntdll!_RtlUserThreadStart+0x1b


STACK_COMMAND:  ~0s ; .cxr ; kb

THREAD_SHA1_HASH_MOD:  7d8c2ec9f442f84c8faab4b784f4842c9f2737ba

FOLLOWUP_IP:
wxmsw30ud_gcc_custom!Z10GetMessageP6tagMSGP6HWND__jj+26
0ca4dfd6 83ec10          sub     esp,10h

FAULT_INSTR_CODE:  c910ec83

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  wxmsw30ud_gcc_custom!Z10GetMessageP6tagMSGP6HWND__jj+26

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: wxmsw30ud_gcc_custom

IMAGE_NAME:  wxmsw30ud_gcc_custom.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  APPLICATION_HANG_wxmsw30ud_gcc_custom!Z10GetMessageP6tagMSGP6HWND__jj+26

PRIMARY_PROBLEM_CLASS:  APPLICATION_HANG_wxmsw30ud_gcc_custom!Z10GetMessageP6tagMSGP6HWND__jj+26

FAILURE_EXCEPTION_CODE:  cfffffff

FAILURE_IMAGE_NAME:  wxmsw30ud_gcc_custom.dll

BUCKET_ID_IMAGE_STR:  wxmsw30ud_gcc_custom.dll

FAILURE_MODULE_NAME:  wxmsw30ud_gcc_custom

BUCKET_ID_MODULE_STR:  wxmsw30ud_gcc_custom

FAILURE_FUNCTION_NAME:  Z10GetMessageP6tagMSGP6HWND__jj

BUCKET_ID_FUNCTION_STR:  Z10GetMessageP6tagMSGP6HWND__jj

BUCKET_ID_OFFSET:  26

BUCKET_ID_MODTIMEDATESTAMP:  0

BUCKET_ID_MODCHECKSUM:  ae87499

BUCKET_ID_MODVER_STR:  3.0.4.0

BUCKET_ID_PREFIX_STR:  APPLICATION_HANG_

FAILURE_PROBLEM_CLASS:  APPLICATION_HANG_wxmsw30ud_gcc_custom!Z10GetMessageP6tagMSGP6HWND__jj+26

FAILURE_SYMBOL_NAME:  wxmsw30ud_gcc_custom.dll!Z10GetMessageP6tagMSGP6HWND__jj

FAILURE_BUCKET_ID:  APPLICATION_HANG_cfffffff_wxmsw30ud_gcc_custom.dll!Z10GetMessageP6tagMSGP6HWND__jj

TARGET_TIME:  2018-09-27T13:36:14.000Z


--- End code ---

The problem is, i have no debug information (symbols ecc) for all this that work with windbg...

BlueHazzard:
I can also confirm that this happens within codeblocks, without patch building and on wx2.8

this seems to be some wxExecute thing...

BlueHazzard:
I think i have fixed this problem. Can you try this patch?

Basically it uses the functionality present in codeblocks, but not used/ deactivated. There is no where written why it is deactivated/not used...

oBFusCATed:
Have you tried git/svn blame?

BlueHazzard:
quite old....

--- Code: ---commit b4ffe10e14c8c1417f89ef671cccc53efa0478f4
Author: Yiannis Mandravellos <mandrav@codeblocks.org>
Date:   Sun May 9 11:51:42 2004 +0000

    Initial import of project


    git-svn-id: https://svn.code.sf.net/p/codeblocks/code/trunk@5 2a5c6006-c6dd-42ca-98ab-0921f2732cef

diff --git a/src/sdk/pipedprocess.cpp b/src/sdk/pipedprocess.cpp
--- /dev/null
+++ b/src/sdk/pipedprocess.cpp
@@ -0,0 +55,22 @@
+{
+    m_Pid = wxExecute(cmd, wxEXEC_ASYNC, this);
+       if (m_Pid)
+       {
+//             m_timerPollProcess.SetOwner(this, idTimerPollProcess);
+//             m_timerPollProcess.Start(pollingInterval);
+       }
+       return m_Pid;
+}
+
+void PipedProcess::SendString(const wxString& text)
+{
+       //Manager::Get()->GetMessageManager()->Log(m_PageIndex, cmd);
+       wxOutputStream* pOut = GetOutputStream();
+       if (pOut)
+       {
+               wxTextOutputStream sin(*pOut);
+               wxString msg = text + '\n';
+               sin.WriteString(msg);
+       }
+}
+
(END)
--- End code ---

Note: my patch is only for testing. The timer is not stopped after the process terminated... there is still some work to do, but first i would like know if this fixes the problem for op

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version