Jack.Jansen@cwi.nl

Here is a screenshot and the call stack:
ntdll.dll!_KiFastSystemCallRet@0()
user32.dll!_NtUserWaitMessage@0() + 0xc bytes
user32.dll!_InternalDialogBox@24() + 0xb6 bytes
user32.dll!_SoftModalMessageBox@4() + 0x677 bytes
user32.dll!_MessageBoxWorker@4() + 0x175 bytes
user32.dll!_MessageBoxTimeoutW@24() + 0x7a bytes
user32.dll!_MessageBoxTimeoutA@24() + 0x9c bytes
user32.dll!_MessageBoxExA@20() + 0x1b bytes
user32.dll!_MessageBoxA@16() + 0x45 bytes
[Frames below may be incorrect and/or missing, no symbols loaded for python25.dll]
kernel32.dll!_CreateFileA@28() + 0x2b bytes
python26.dll!1e00f11b()
python26.dll!1e00c7b5()
python26.dll!1e007ac3()
python26.dll!1e01cceb()
msvcr90.dll!_sopen_helper(const char * path=0x0fd0dc68, int oflag=32768, int shflag=64, int pmode=384, int * pfh=0x0fd0d7c8, int bSecure=1) Line 190 + 0x5 bytes
msvcr90.dll!_sopen_s(int * pfh=0x0fd0d7c8, const char * path=0x0fd0dc68, int oflag=32768, int shflag=64, int pmode=384) Line 907 + 0x16 bytes
msvcr90.dll!_openfile(const char * filename=0x1e1a53b2, const char * mode=0x1e0097c7, int shflag=265345024, _iobuf * str=0x00000025) Line 272 + 0x17 bytes
00000025()
python26.dll!1e0094af()
python26.dll!1e01cf9d()
msvcr90.dll!__lock_fhandle(int fh=89305032) Line 468 + 0x5 bytes
NMMediaServer.dll!initMediaHomeWebInterface() Line 32 + 0x30 bytes C++
python26.dll!1e025c0d()
python26.dll!1e020bc3()
python26.dll!1e026cf5()
python26.dll!1e026d27()
ntdll.dll!_RtlGetFullPathName_Ustr@24() + 0x2f7 bytes
python26.dll!1e00ed6e()
python26.dll!1e009136()
python26.dll!1e00fcc6()
python26.dll!1e00919a()
python26.dll!1e0157a1()
ntdll.dll!_RtlAllocateHeapSlowly@12() + 0x3da bytes
msvcr90.dll!malloc(unsigned int size=408) Line 163 + 0x5f bytes
The problem is msvcr90.dll? Why this dll for Visual Studio 2008? I thought it should be 2005. :-?

On 20-Oct-2008, at 15:24 , anti00Zero wrote:
The problem is msvcr90.dll? Why this dll for Visual Studio 2008? I
thought it should be 2005. :-?
That could be the problem, indeed. So maybe Python 2.6 was built with
VS2008?? Does anyone know?
--
Jack Jansen, <Jack.Jansen@cwi.nl>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma
Goldman

On 2008-10-21 11:46, Jack Jansen wrote:
Python 2.6 is being build with Visual Studio 2008 Professional Edition.
The marketing name maps to VC9.0 and the code needs the msvcr90.dll as runtime.
-- Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Source (#1, Oct 21 2008)
:::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611

On 20-Oct-2008, at 15:24 , anti00Zero wrote:
The problem is msvcr90.dll? Why this dll for Visual Studio 2008? I
thought it should be 2005. :-?
That could be the problem, indeed. So maybe Python 2.6 was built with
VS2008?? Does anyone know?
--
Jack Jansen, <Jack.Jansen@cwi.nl>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma
Goldman

On 2008-10-21 11:46, Jack Jansen wrote:
Python 2.6 is being build with Visual Studio 2008 Professional Edition.
The marketing name maps to VC9.0 and the code needs the msvcr90.dll as runtime.
-- Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Source (#1, Oct 21 2008)
:::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611
participants (3)
-
anti00Zero
-
Jack Jansen
-
M.-A. Lemburg