Opened 14 years ago

Closed 10 years ago

#234 closed defect (fixed)

setup crashes in win64, windows server 2003

Reported by: warmerdam Owned by: warmerdam
Priority: normal Milestone:
Component: OSGeo4W Keywords:
Cc: tamas

Description

Tamas and I have experienced crashes of the installer before the first window comes up. Tamas on win64, and me on Windows Server 2003. The same problem does not occur with the distributed cygwin setup.exe.

A debug traceback indicates it occurs in the call to OpenProcessToken?() in the is_admin() function.

Change History (4)

comment:1 Changed 14 years ago by warmerdam

Status: newassigned

In r1027, r1028 and r1029 I have added a hacky "--safe" mode that skips a bunch of win32 calls related to administrative capabilities. This safe mode can be turned on with the --safe commandline switch to setup. I would consider making this the default, but I don't really understand what the code I'm disabling does.

The changes can be seen at:

http://trac.osgeo.org/osgeo/changeset?new=osgeo4w%2Fsetup%401029&old=osgeo4w%2Fsetup%401026

Tamas, I'm uploading a new osgeo4w-setup.exe. I'd appreciate it if you could test it sometime on win64 (passing the --safe switch) and see if it works.

My debugging conditions on my test win2003 server were very painful (remote desktop over a very high latency link) so I did not try and do a good job of debugging, just hack around the problem code. Further analysis of this problem will be needed some day.

comment:2 Changed 14 years ago by warmerdam

Tamas writes:

I've just tried the current installer (compressed) and the yesterday's version and both were working pretty well on my Win2003 x64 R2. I wonder why you've found such problems with the current version.

...

I'd add to my previous statements that the big setup cannot be renamed. If I rename the file eg. to osgeo4w-setup1.exe then the crashing issue is stepping up. The compressed version can be renamed without problems though.

Frank writes:

I wonder if you have an opinions on why this might be? I'm getting the impression there is something that is corrupting the stack or heap in a subtle way and it is very sensitive to details of memory layout and code arrangement. But, I don't really know how to dig into the problem and try to resolve it.

comment:3 Changed 14 years ago by warmerdam

I've not had any problems with setup on WinXP Professional x64, SP2 (other than the ones previously documented, which I don't believe are related). The last setup I used is:

20/03/2008 04:24 PM 1,144,320 osgeo4w-setup.exe

cheers,

matt wilkie

comment:4 Changed 10 years ago by maphew

Resolution: fixed
Status: assignedclosed

Closed as too old to be relevant anymore. If this is still a problem please open a new ticket at http://trac.osgeo.org/osgeo4w

Note: See TracTickets for help on using tickets.