On Jul 30 18:44, Corinna Vinschen wrote:
> Hi folks,
>
>
> I just uploaded a new Cygwin 1.7 test release, 1.7.0-53.
I removed the -53 test release from cygwin.com. There's a bug which
apparently only occurs in code build with optimization. My local debug
version works, but I have no time to de
> The only way was to back out to the previous version (1.7.0-52)
I'm in the same boat, launching bash.exe with the -53 build was a no-go:
5 [main] bash 5604 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
1600 [main] bash 5604 open_stackdumpfile: Dumping stack trace to
ba
I rebooted - no go
I re-installed - no go
The only way was to back out to the previous version (1.7.0-52)
- Jim
On Thu, Jul 30, 2009 at 12:40 PM, Jim Reisert
AD1C wrote:
> Since the update, nothing works. Here is output from "uname":
>
>
> 3 [main] uname 8664 _cygtls::handle_exceptions: E
Since the update, nothing works. Here is output from "uname":
3 [main] uname 8664 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
406 [main] uname 8664 open_stackdumpfile: Dumping stack trace to
uname.exe.stackdump
423630 [main] uname 8664 _cygtls::handle_exceptions: Ex
Hi folks,
I just uploaded a new Cygwin 1.7 test release, 1.7.0-53.
That's really the last test release. Hopefully.
The two problems which had to be fixed are partially fixed now.
You know the drill by now, see the older test release announcements
as http://cygwin.com/ml/cygwin-announce/2009-0
5 matches
Mail list logo