[pywin32-bugs] [ pywin32-Bugs-1448160 ] Win2003 dual-core crash on startup
OLD project page for the Python extensions for Windows
Brought to you by:
mhammond
From: SourceForge.net <no...@so...> - 2006-09-22 12:49:24
|
Bugs item #1448160, was opened at 2006-03-12 17:09 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1448160&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: Darren (zaphod72) Assigned to: Nobody/Anonymous (nobody) Summary: Win2003 dual-core crash on startup Initial Comment: I have a dual-core Windows Server 2003 and a single- core server also running Windows Server 2003. On the dual-core pythonwin crashes on startup, shortly after displaying the UI. On the single-core it works fine. Here's the crash info from WinDbg - (ee8.8b8): Access violation - code c0000005 (!!! second chance !!!) eax=00000000 ebx=773e20e0 ecx=000080a2 edx=001668d8 esi=0013fcf8 edi=7ffdf6cc eip=00a0180c esp=0013fcd4 ebp=0013fd04 iopl=0 nv up ei pl zr na po nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246 00a0180c 58 pop eax And the stack trace - ChildEBP RetAddr Args to Child WARNING: Frame IP not in any known module. Following frames may be wrong. 0013fcd0 77387050 000080a2 00000000 00000000 0xa0180c 0013fd04 77387dc3 00a0180c 000080a2 00000000 USER32! UserCallDDECallback+0x23 0013fd3c 77387101 0015ca78 000080a2 00000000 USER32! DoCallback+0x6a 0013fd74 7738e3f0 0015ca78 000004c8 0000c02c USER32! ProcessRegistrationMessage+0xa4 0013fd8c 7739c3b7 001500ce 000004c8 0000c02c USER32! DDEMLMotherWndProc+0x2c 0013fdb8 7739c484 7738e3ad 001500ce 000004c8 USER32! InternalCallWinProc+0x28 0013fe30 7739c73c 00000000 7738e3ad 001500ce USER32! UserCallWinProcCheckWow+0x151 0013fe98 7738e406 00155998 00000001 00000000 USER32! DispatchMessageWorker+0x327 0013fea8 7c169076 00155998 00155998 00403040 USER32! DispatchMessageA+0xf 0013feb8 7c16913e 00403040 1e055870 0013ffc0 MFC71! AfxInternalPumpMessage+0x3e 0013fed4 1e2b6767 00403040 ffffffff 00000000 MFC71! CWinThread::Run+0x54 0013ffc0 77e523cd 00000000 00000000 7ffdc000 win32ui! Python_callback+0x1247 0013fff0 00000000 0040186c 00000000 78746341 kernel32! BaseProcessStart+0x23 I didn't try to build the source. But if I can get the pdb files then I'd be happy to try and get some more information (darrenk at yahoo). Thanks ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2006-09-22 22:49 Message: Logged In: YES user_id=14198 I'm guessing this will work with -nodde specified on the command-line. I'd love to remove that - sadly the DDE code is fairly intractable :( I wouldn't know where to ask you to start with the .pdb files ---------------------------------------------------------------------- Comment By: kxroberto (kxroberto) Date: 2006-03-15 03:57 Message: Logged In: YES user_id=972995 Good to get more about this dual core bug (following #1442426 & #1441884 ) Can you maybe try this bug also with py2.3.5 / build 205 ? (build 207 doesn't work for py2.3). You can simply run a second py2.3 installation parallel on your computer. Such test would exclude the py2.4/MFC7.1 scheme as reason for the crash. I sent you that win32ui with .pdb: That should provide detailed stack traces. --- related: #1442426 , #1441884 http://sourceforge.net/tracker/index.php?func=detail&aid=1441884&group_id=5470&atid=105470 --- I got similar user reports for a win32ui-app (build 203/MFC4.2/py2.3.5; even without pythonwin IDE). Unfortunately I got no stack traces. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1448160&group_id=78018 |