From: "Thrall, Bryan" <bryan.thrall@flightsafety.com>
To: <cygwin-apps@cygwin.com>
Subject: RE: CVS setup.exe crashes on Windows 2003 Server x64
Date: Mon, 22 Jan 2007 19:00:00 -0000 [thread overview]
Message-ID: <297343D29C14AA4D822142893ABEAEF302A6A2FB@srv1163ex1.flightsafety.com> (raw)
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 it invalid at that point and valid after the segfault?).
>
> Setup.exe does contain some self-modifying code. It is in the file
> autoload.c, and deals with automatic loading of certain DLLs not
> present on all Windows versions.
>
> Glancing at it, it looks very 32-bit specific. It seems fairly
> miraculous that it works at all on LP64, actually, considering it
> casts pointers to int.
>
> Max.
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 hasn't been
changed since 2004...
--
Bryan Thrall
FlightSafety International
Bryan.Thrall@flightsafety.com
next reply other threads:[~2007-01-22 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 19:00 Thrall, Bryan [this message]
2007-01-22 19:10 ` Brian Dessent
-- strict thread matches above, loose matches on Subject: below --
2006-12-18 15:39 Thrall, Bryan
2007-01-13 17:30 ` Max Bowsher
2006-12-18 14:45 Thrall, Bryan
2006-12-18 15:03 ` Dave Korn
2006-12-15 21:08 Thrall, Bryan
2006-12-16 1:13 ` Dave Korn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=297343D29C14AA4D822142893ABEAEF302A6A2FB@srv1163ex1.flightsafety.com \
--to=bryan.thrall@flightsafety.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).