Max Bowsher wrote on Saturday, January 13, 2007 11:30 AM:
Thrall, Bryan wrote:
... And in fact, disabling DEP for setup.exe fixes the problem. So,
it looks like setup.exe is trying to execute some memory that Windows
thinks it shouldn't be (the invalid this pointer, probably, but why
then is
Thrall, Bryan wrote:
Well, I believe Win2k3 Server x64 has a 32-bit compatibility mode that
it is using to run setup.exe. Self-modifying code would explain why DEP
would kill the program, but does that explain why CVS setup.exe is
getting killed but 2.510.2.2 isn't? It looks like autoload.c
Thrall, Bryan wrote:
... And in fact, disabling DEP for setup.exe fixes the problem. So, it
looks like setup.exe is trying to execute some memory that Windows
thinks it shouldn't be (the invalid this pointer, probably, but why then
is it invalid at that point and valid after the segfault?).
Dave Korn wrote on Friday, December 15, 2006 7:13 PM:
On 15 December 2006 21:08, Thrall, Bryan wrote:
I'm seeing setup.exe built from CVS head crash on Windows 2003 Server
x64 (Standard version, SP 1).
Program received signal SIGSEGV, Segmentation fault.
0x004eb157 in [EMAIL PROTECTED] ()
On 18 December 2006 14:45, Thrall, Bryan wrote:
Dave Korn wrote on Friday, December 15, 2006 7:13 PM:
On 15 December 2006 21:08, Thrall, Bryan wrote:
I'm seeing setup.exe built from CVS head crash on Windows 2003 Server
x64 (Standard version, SP 1).
Program received signal SIGSEGV,
Dave Korn wrote on Monday, December 18, 2006 9:04 AM:
On 18 December 2006 14:45, Thrall, Bryan wrote:
Dave Korn wrote on Friday, December 15, 2006 7:13 PM:
On 15 December 2006 21:08, Thrall, Bryan wrote:
I'm seeing setup.exe built from CVS head crash on Windows 2003
Server x64 (Standard
On 15 December 2006 21:08, Thrall, Bryan wrote:
I'm seeing setup.exe built from CVS head crash on Windows 2003 Server
x64 (Standard version, SP 1).
Program received signal SIGSEGV, Segmentation fault.
0x004eb157 in [EMAIL PROTECTED] ()
(gdb) bt
#0 0x004eb157 in [EMAIL PROTECTED] ()
#1
