public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-xfree@cygwin.com
Subject: Re: XWin.exe segmentation fault on Windows 7
Date: Tue, 14 Aug 2012 09:53:00 -0000	[thread overview]
Message-ID: <20120814095226.GA14802@calimero.vinschen.de> (raw)
In-Reply-To: <CACAZVOxZHJvqtCpgat4=4APvi5eZ_aBUHfmcdRtrEMzQsYgjig@mail.gmail.com>

On Aug 14 16:41, Chris LeBlanc wrote:
> > Now the question is, if the same problem occurs, why?  Please paste
> > the contents of /etc/fstab and, if it exists, /etc/fstab.d/$USER
> > into your reply.
> 
> Thanks for the information, I think we're getting closer to finding the problem.
> 
> /etc/fstab doesn't have anything in it apart from comments, and the
> /etc/fstab.d directory is empty.
> 
> Here is the output from the mount command:
> C:/cygwin/bin on /usr/bin type ntfs (binary,auto)
> C:/cygwin/lib on /usr/lib type ntfs (binary,auto)
> C:/cygwin on / type ntfs (binary,auto)
> C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
> E: on /cygdrive/e type ntfs (binary,posix=0,user,noumount,auto)
> Segmentation fault (core dumped)
> 
> It fails when it reaches a network share.  Looking at them in Windows
> Explorer, they're all NcFsd network shares ...

That was the essential information to find the bug.  For the last
Cygwin version I added support for the new ReFS filesystem and I
changed one datastructure without also changing another, closely
related datastructure.  The bug would have shown for other FSes
as well, but it would only have resulted in printing the wrong
FS type in mount.  Only for NcFsd it was bound to crash.

This will be fixed in the (soon to come) Cygwin 1.7.17.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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


      reply	other threads:[~2012-08-14  9:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  4:51 Chris LeBlanc
2012-08-08 13:03 ` Jon TURNEY
2012-08-08 23:19   ` Chris LeBlanc
2012-08-09  2:19     ` Mark Geisert
2012-08-09  4:55       ` Chris LeBlanc
2012-08-13  4:24         ` Chris LeBlanc
2012-08-13 12:17           ` Jon TURNEY
2012-08-13 12:42             ` Corinna Vinschen
2012-08-14  4:42               ` Chris LeBlanc
2012-08-14  9:53                 ` Corinna Vinschen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120814095226.GA14802@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).