Re: [1.7] Updated: cygwin-1.7.0-53

2009-07-30 Thread Jim Reisert AD1C
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: Exception:
STATUS_ACCESS_VIOLATION
 456780 [main] uname 8664 _cygtls::handle_exceptions: Error while
dumping state (probably corr
upted stack)
 490396 [main] uname 8664 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
 523408 [main] uname 8664 _cygtls::handle_exceptions: Error while
dumping state (probably corr
upted stack)
 556741 [main] uname 8664 _cygtls::handle_exceptions: Exception:
STATUS_ILLEGAL_INSTRUCTION
 595881 [main] uname 8664 _cygtls::handle_exceptions: Error while
dumping state (probably corr
upted stack)


On Thu, Jul 30, 2009 at 10:44 AM, Corinna
Vinschencorinna-cyg...@cygwin.com wrote:
 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-07/msg00012.html

 Btw., the User's Guide is also available as PDF now:
 http://cygwin.com/1.7/cygwin-ug-net/cygwin-ug-net.pdf


 What's new in contrast to 1.7.0-52
 ===

 - Recognize non-NTFS remote filesystems which report to be NTFS as
  cifs filesystems and avoid to call potentially unsupported NT call
  in readdir().
  http://cygwin.com/ml/cygwin/2009-06/msg01008.html


 Bugfixes:
 =

 - Don't just return EBUSY when trying to remove shared files on an NFS
  share.  Rather, really try to remove them first.
  http://cygwin.com/ml/cygwin/2009-07/msg00872.html

 - Fix a typo in setlocale() which made the GBK charset disfunctional.
  http://cygwin.com/ml/cygwin/2009-07/msg00875.html

 - Partially fix the FIFO regression reported in
  http://cygwin.com/ml/cygwin/2009-07/msg00233.html

 - Fix a crash when trying to set long console title strings.
  http://cygwin.com/ml/cygwin/2009-07/msg00893.html

 - Lower the memory usage of file descriptor data on the Cygwin heap.
  This avoids to allocate 64K chunks per file.  The new size is about
  250 bytes + 4 * path length.  This should fix the problem reported in
  http://cygwin.com/ml/cygwin/2009-07/msg00766.html

 - Fix a problem in the destructor call order on process exit.
  http://cygwin.com/ml/cygwin-developers/2009-07/msg0.html

 - Fix handling of incomplete UTF-8 sequences and rework UTF-16 surrogate
  pair handling in mbrtowc() to be more bullet-proof.  Check for invalid
  Unicode valus beyond 0x10.
  http://cygwin.com/ml/cygwin/2009-07/msg00941.html


 FAQ:
 

 - Q: How do I know that I'm running Cygwin 1.7.0-53?

  A: The `uname -v' command prints 2009-07-30 18:01


 Have fun,
 Corinna


              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

 If you want to unsubscribe from the cygwin-announce mailing list, look
 at the List-Unsubscribe:  tag in the email header of this message.
 Send email to the address specified there.  It will be in the format:

 cygwin-announce-unsubscribe-you=3d3dyourdomain@cygwin.com

 If you need more information on unsubscribing, start reading here:

 http://cygwin.com/lists.html#unsubscribe-simple

 Please read *all* of the information on unsubscribing that is available
 starting at this URL.

 --
 Corinna Vinschen                  Please, send mails regarding Cygwin to
 Cygwin Developer                                mailto:cygwin@cygwin.com
 Red Hat, Inc.




-- 
Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us

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



Re: [1.7] Updated: cygwin-1.7.0-53

2009-07-30 Thread Jim Reisert AD1C
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
AD1Cjjreis...@alum.mit.edu wrote:

 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: Exception:
 STATUS_ACCESS_VIOLATION
  456780 [main] uname 8664 _cygtls::handle_exceptions: Error while
 dumping state (probably corr
 upted stack)
  490396 [main] uname 8664 _cygtls::handle_exceptions: Exception:
 STATUS_ACCESS_VIOLATION
  523408 [main] uname 8664 _cygtls::handle_exceptions: Error while
 dumping state (probably corr
 upted stack)
  556741 [main] uname 8664 _cygtls::handle_exceptions: Exception:
 STATUS_ILLEGAL_INSTRUCTION
  595881 [main] uname 8664 _cygtls::handle_exceptions: Error while
 dumping state (probably corr
 upted stack)


-- 
Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us

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



Re: [1.7] Updated: cygwin-1.7.0-53

2009-07-30 Thread Chris Sutcliffe
 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
bash.exe.stackdump
 148227 [main] bash 5604 _cygtls::handle_exceptions: Exception:
STATUS_ILLEGAL_INSTRUCTION
 170978 [main] bash 5604 _cygtls::handle_exceptions: Error while
dumping state (probably corrupted s
tack)

Chris

-- 
Chris Sutcliffe
http://emergedesktop.org

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