public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net> To: cygwin-xfree@cygwin.com Subject: Re: X server crash when running texworks Date: Mon, 02 Apr 2012 22:50:00 -0000 [thread overview] Message-ID: <4F7A2D26.8000103@users.sourceforge.net> (raw) In-Reply-To: <4F7A16A1.5030100@cornell.edu> On 2012-04-02 16:14, Ken Brown wrote: > Much earlier in the thread I mentioned a warning "QFileSystemWatcher: > failed to add paths: /home/kbrown". I've looked at the QtCore sources, > and that warning is generated by the function > QFileSystemWatcher::addPaths, in corelib/io/qfilesystemwatcher.cpp. If > I'm understanding the code correctly, that function tries to use a > "native" (system-specific) FileSystemWatcherEngine if possible. The > function QFileSystemWatcherPrivate::createNativeEngine in the same file > creates native engines on Windows, Linux, FreeBSD, Mac OS, and Symbian, > but not on Cygwin. Correct, as the Windows backend won't work OOTB with *NIX filesystem, and we don't support any of the other native backends. > I don't know if it's worth pursuing this, but the failure of > FileSystemWatcher could conceivably be the problem here. Do you know > enough about Qt to have any ideas about how to proceed? Or Yaakov? The only plausible solutions would be to either: * implement inotify[1] in Cygwin on top of Windows' Directory Change Notification APIs[2] (which would benefit a number of packages); * OR implement a FAM/Gamin-based QFileSystemWatcher backend. Yaakov [1] http://man7.org/linux/man-pages/man7/inotify.7.html [2] http://msdn.microsoft.com/en-us/library/windows/desktop/aa365261%28v=vs.85%29.aspx -- 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/
next prev parent reply other threads:[~2012-04-02 22:50 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-24 19:48 Ken Brown 2012-03-26 19:47 ` Ken Brown 2012-03-26 20:07 ` Jon TURNEY 2012-03-26 20:33 ` Ken Brown 2012-03-28 11:16 ` Jon TURNEY 2012-03-28 12:28 ` Ken Brown 2012-03-28 12:46 ` Ken Brown 2012-03-29 12:14 ` Jon TURNEY 2012-03-29 20:00 ` Ken Brown 2012-03-29 20:21 ` Yaakov (Cygwin/X) 2012-03-29 21:01 ` Ken Brown 2012-03-30 11:36 ` Jon TURNEY 2012-03-31 10:29 ` Jon TURNEY 2012-03-31 15:27 ` Ken Brown 2012-04-01 6:07 ` Jim Reisert AD1C 2012-04-01 13:36 ` Jon TURNEY 2012-04-02 12:05 ` Ken Brown 2012-04-02 16:06 ` Jim Reisert AD1C 2012-04-02 21:14 ` Ken Brown 2012-04-02 22:50 ` Yaakov (Cygwin/X) [this message] 2012-04-01 13:40 ` Jon TURNEY 2012-03-28 9:35 ` Yaakov (Cygwin/X)
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=4F7A2D26.8000103@users.sourceforge.net \ --to=yselkowitz@users.sourceforge.net \ --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: linkBe 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).