[lxml-dev] [Fwd: [Bug 263898] [NEW] Windows Installer crashes due to access violation]

[Stefan Behnel]

Hi,

has anyone seem this before or could someone please test if this is
reproducible on other machines?

Thanks,
Stefan

--------------------------------------------------------------------------
Subject: [Bug 263898] [NEW] Windows Installer crashes due to access violation
--------------------------------------------------------------------------

Public bug reported:

I tried to install lxml-2.1.1.win32-py2.5.exe on my WinXP PC and got the
attached
crash from the installer.
It happened after confirming all settings and clicking the "Next" button
on the "Ready to install" page
of the installer.

Using Visual Studio Debugger to investigate crash :

Callstack :
 	ntdll.dll!_RtlEnterCriticalSection at 4()  + 0xb
 	msvcr71.dll!_lock_file(void * pf=0x00000000)  Line 236	C
>	msvcr71.dll!fprintf(_iobuf * str=0x00000000, const char *
format=0x0012d278, ...)  Line 63 + 0x6	C
 	lxml-2.1.1.win32-py2.5.exe!00402ca8()
 	user32.dll!77d48734()
 	user32.dll!77d48bd9()
 	user32.dll!77d541dc()
 	user32.dll!77d541a9()
 	user32.dll!77d53fd9()
 	ntdll.dll!_RtlpFreeToHeapLookaside at 8()  + 0x26
 	ntdll.dll!_RtlFreeHeap at 12()  + 0x114
 	ntdll.dll!_RtlpFreeAtom at 4()  + 0x1b
 	c5ffffff()

Looking at the fprintf function I can see that "str" variable is NULL.
_lock_file function using NULL pointer the access struture variable which
eventually results in the reported crash.

** Affects: lxml
     Importance: Undecided
         Status: New

-- 
Windows Installer crashes due to access violation
https://bugs.launchpad.net/bugs/263898