This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: XWin core dump
- From: Joe Bronkema <joseph dot d dot bronkema at lmco dot com>
- To: Harold Hunt <huntharo at msu dot edu>
- Cc: cygwin-xfree at cygwin dot com
- Date: Thu, 28 Mar 2002 12:59:28 -0500
- Subject: Re: XWin core dump
- Organization: Lockheed Martin NE&SS-Moorestown
- References: <NHEELHJHHFKPMAEAFMFCIEIGCMAA.huntharo@msu.edu>
Harold,
I did an actual file search.
Joe
Harold Hunt wrote:
>
> Joe,
>
> Have you done an actual file search for multiple versions of cygwin1.dll, or
> have you just assumed that since you only installed Cygwin once that you
> only have one copy of cygwin1.dll? If you've just assumed, then you need to
> do a file search, as lots of software comes with its own copy of
> cygwin1.dll.
>
> Let us know which it is,
>
> Harold
>
> > -----Original Message-----
> > From: cygwin-xfree-owner@cygwin.com
> > [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Joe Bronkema
> > Sent: Thursday, March 28, 2002 9:41 AM
> > To: cygwin-xfree@cygwin.com
> > Subject: XWin core dump
> >
> >
> > Hi,
> >
> > I tried Cygwin/XFree for the first time today, and was unpleasantly
> > surprised with a core dump when I tried to start the server.
> >
> > I'm running Windows 95 with Cygwin 1.3.10 and the 4.2.0 binaries from
> > mirrors.rcn.net. Here's the stack dump:
> >
> > $ cat XWIN.EXE.stackdump
> > Exception: STATUS_ACCESS_VIOLATION at eip=19E0C48A
> > eax=82BBAE20 ebx=00000000 ecx=00000000 edx=00A4EBE8 esi=82BBA00C
> > edi=82BBA040
> > ebp=00A4EC00 esp=00A4EBBC program=C:\CYGWIN\USR\X11R6\BIN\XWIN.EXE
> > cs=0157 ds=015F es=015F fs=361F gs=0000 ss=015F
> > Stack trace:
> > Frame Function Args
> > 00A4EC00 19E0C48A (00000000, 000000C0, 46000000, 82BBA00C)
> > 017D1AC8 00021401 (FFFFFFFF, FFFFFFFF, FFFFFFFF, FFFFFFFF)
> > 0179E578 01786E3A (017D1AC8, 0974F18B, 2BC4E856, C483FFFC)
> > 6029107 [main] XWin 586635 handle_exceptions: Error while dumping state
> > (probabl
> > y corrupted stack)
> >
> > I checked the FAQ. The entry for STATUS_ACCESS_VIOLATION suggested
> > multiple conflicting versions of cygwin1.dll. I have only the one.
> >
> > Any ideas? Any additional info I could provide that would help?