[pywin32-bugs] [ pywin32-Bugs-1445659 ] build 207 & 206 for py2.3 : pythonwin.exe startup crash

[SourceForge.net <no...@so...>]

Bugs item #1445659, was opened at 2006-03-08 15:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1445659&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: Robert Kiendl (kxroberto)
Assigned to: Nobody/Anonymous (nobody)
Summary: build 207 & 206 for py2.3 : pythonwin.exe startup crash

Initial Comment:
build 207 (and 206) for Python 2.3(.5)
on WinXP Home (SR1) / normal single core CPU : 

Pythonwin.exe doesn't start: Crash:

Instruction 0x1e037435 points to memory 0x00000028...

MSVC++ Runtime Library : Runtime Error!

debugger shows stack:

PYTHON23! 1e037435()
MFC42! 73d3c10b()
MFC42! 73d42167()


build 205 for 2.3 is the last build which starts ok. I
lived so far with build 203 - also ok.

reproducable.

-------

Additional Notes:

When I start 207/2.3's framework with attached
startupframework.py (or start_pythonwin.pyw) instead of
pythonwin.exe it works! (?)

When I try to use 205/2.3's 5 files
pythonwin.exe,win32ui.pyd,win32uiole.pyd,dde.pyd,scintilla.dll
in otherwise 207/2.3, the crash is the same. guess its
something in the plain python code or win32 modules.

build 207 pythonwin.exe for py2.4 works on my machine,
the described bug seems specific for py2.3 (/MFC42?).

starting build 207/2.4 with start_pythonwin.pyw is (of
course) also ok. But when I close the framework, one of
that old win32ui close crash bug winks: memory
violation at (see also PS below):

011402a0()
MFC71! 7c176020()
MFC71! 7c16e0b0()
MFC71! 7c16e14f()
MFC71! 7c16e1b8()
MFC71! 7c16e1f6()
USER32! 77d18654()
USER32! 77d18723()
USER32! 77d19153()
USER32! 77d19196()
NTDLL! 77f65da3()
WIN32UI! 1e2c8691()
PYTHON24! 1e1ae378()


Robert

--------

PS: Serious old bug 1048355 (causes crashes) in win32ui
is still not addressed in 207. T::OnNotify crashes when
e.g. WM_NCDESTROY pulls off the underlying window out
of MFC during Python_OnNotify. To get my apps stable i
have to patch OnNotify & OnCmdMsg in win32uiExt.h (only
2 lines added) as shown below (suspect
CPythonRichEditView::OnNotify and
CPythonPropertySheet::OnNotify and
CPythonDocTemp<P>::OnCmdMsg and
CPythonRichEditView::OnCmdMsg and
CPythonPropertySheet::OnCmdMsg to require all the same
patch - often when win32ui apps close, strange crashes
occure... ):

	virtual BOOL OnCmdMsg( UINT nID, int nCode, void*
pExtra, AFX_CMDHANDLERINFO*pHandlerInfo )
	{
		// yield to Python first
		if (Python_OnCmdMsg (this, nID, nCode, pExtra,
pHandlerInfo))
			return TRUE;
		else {
			if (!IsWindow( this->m_hWnd ))
				return TRUE;			
			return T::OnCmdMsg (nID, nCode, pExtra, pHandlerInfo);
		}
	}
	virtual BOOL OnNotify (WPARAM wParam, LPARAM lParam,
LRESULT *pResult) {
		// yield to Python first
		if (Python_OnNotify (this, wParam, lParam, pResult))
			return TRUE;
		else {
			if (!IsWindow( this->m_hWnd ))
			//if (!IsWindow( ((NMHDR*)lParam)->hwndFrom ))
				return TRUE;			
			return T::OnNotify (wParam, lParam, pResult);
		}
	}



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1445659&group_id=78018