nearly all postinstall scripts segfaulting in 64bit Windows (XP + Vista)

Lonni J Friedman netllama@gmail.com
Tue Dec 16 20:22:00 GMT 2008


On Fri, Nov 21, 2008 at 1:51 PM, Larry Hall (Cygwin)
<reply-to-list-only-lh@cygwin.com> wrote:
> Lonni J Friedman wrote:
>>
>> On Thu, Nov 20, 2008 at 3:40 PM, Lonni J Friedman wrote:
>>>
>>> Greetings,
>>> I'm attempting to setup a build environment, which happens to require
>>> cygwin.  I ran into no problems getting this up with 32bit Windows XP,
>>> however for both WINXP64 and VISTA64, the cygwin installation blows up
>>> badly while running all of the postinstall scripts (in
>>> /etc/postinstall).  Nearly all of them are segfaulting.
>>>
>>> For example, if I attempt to run /etc/postinstall/bash.sh manually, it
>>> churns for a few seconds, and then dies with the following output:
>>> 11 [main] bash 1644 +_cygtls::handle_exceptions: Error while dumping
>>> state ( probably a corrupted stack)
>>> Segmentation fault (core dumped)
>>>
>>> The only potential oddity in this equation is that my Windows (both 32
>>> & 64bit) installations are inside of Xen (running on a Linux system).
>>>
>>> I'm at a complete loss on how to debug this at this point.  Any and
>>> all suggestions are gratefully accepted.
>>
>> No suggestions?  Anyway, it also looks like I'm getting a stackdump
>> every dump this segfaults which includs the following:
>> ######
>> Exception: STATUS_ACCESS_VIOLATION at eip=7D61C95D
>> eax=00000000 ebx=0022C4D8 ecx=00000000 edx=00000000 esi=FFFFFFFE
>> edi=FFFFFFFF
>> ebp=0022C4A8 esp=0022C45C program=C:\cygwin\bin\bash.exe, pid 924, thread
>> main
>> cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
>> Stack trace:
>> Frame     Function  Args
>> 0022C4A8  7D61C95D  (00000274, FFFFFFFE, 0022C4D8, 00000001)
>> 61169E30  6101CDEB  (0000000F, 80100000, 00000274, 00000000)
>> 6113F9B8  0000044F  (610FE560, 610FE530, 610FDB40, 6101E4A0)
>> 610FE950  610FDB70  (90909090, 90909090, 90C3C031, 90909090)
>>     11 [main] bash 924 _cygtls::handle_exceptions: Error while
>> dumping state (probably corrupted stack)
>> ######
>
> There's been one other report, that I recall, of problems running
> Cygwin under Xen but AFAIK, no one on the list who's digging into
> the code is using it (or at least seeing the problem when using it.)
> Whatever the problem is, it seems specific to Xen since other VMs run
> Cygwin fine.  Certainly the stack suggests that the crash happens in
> bash and not the Cygwin DLL, though I'm not sure that this says much.
> ;-)

FWIW, I found the 'one other report' here:
http://www.cygwin.com/ml/cygwin/2008-11/msg00112.html

Unfortunately, both he & I are both at a loss on how to make any
headway on this.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list