This is the mail archive of the
cygwin-patches@cygwin.com
mailing list for the Cygwin project.
Re: Strange problem with Cygwin from CVS
- From: Corinna Vinschen <vinschen at redhat dot com>
- To: cygwin-patches at cygwin dot com
- Date: Thu, 13 May 2004 21:34:49 +0200
- Subject: Re: Strange problem with Cygwin from CVS
- References: <BAY9-F14904H3Nztw4500030904@hotmail.com>
- Reply-to: cygwin-patches at cygwin dot com
On May 13 14:09, Stephen Cleary wrote:
> So, I backed out my patch, and was just compiling the Cygwin CVS, and got
> the same thing. I tried it again at lunch today (thinking that someone may
> have committed something incorrectly and it would soon be fixed) - same
> problem. Is anyone else seeing this?
>
> Here's what I'm doing:
> [from /cygdrive/c/cygwin-cvs] cvs update -C
> [from /cygdrive/c/cygwin-cvs/obj] make
> [using a .cmd file] move the new-cygwin1.dll over
> c:\cygwin\bin\cygwin1.dll, also delete the generated cygwin0.dll
>
> After this procedure, starting bash will display the following in the
> console:
> 4 [main] bash 320 handle_exceptions: Exception:
> STATUS_ACCESS_VIOLATION
> 1059 [main] bash 320 open_stackdumpfile: Dumping stack trace to
> bash.exe.stackdump
>
> I'm attaching the stackdump file if that's any help.
>
> So, my main question is: is anyone else seeing this, or has something on my
> machine gotten screwed up?
WFM. Try "make clean; make".
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Co-Project Leader mailto:cygwin@cygwin.com
Red Hat, Inc.