unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: michael.albinus@gmx.de, 13540@debbugs.gnu.org
Subject: bug#13540: 24.3.50; Regression in trunk: auto-revert-mode fails on files accessed via samba
Date: Thu, 24 Jan 2013 20:16:57 +0200	[thread overview]
Message-ID: <83r4lala3q.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0gdqnnpcQxcjhN-mTkGfof9F8bCwynton8vWpiKx9_XWw@mail.gmail.com>

> Date: Thu, 24 Jan 2013 18:44:56 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: Michael Albinus <michael.albinus@gmx.de>, 13540@debbugs.gnu.org
> 
>   (gdb) run
>   Starting program: C:\emacs\emacs-24.3.50\bin\emacs.exe -Q
>   [New Thread 5892.0xc44]
>   [New Thread 5892.0x1418]
>   [New Thread 5892.0x16c8]
>   [New Thread 5892.0x16a0]
>   [New Thread 5892.0x1700]
>   [New Thread 5892.0x158c]
>   [New Thread 5892.0x171c]

Each time you evaluate the expression that calls w32notify-add-watch,
you should see another "New Thread" announcement.  This is normal,
since each watch you add starts a new thread where the watching code
runs.

Can you use Process Explorer or "pslist -d emacs" (both tools are from
the Sysinternals package) to see if the threads started when you
invoke w32notify-add-watch keep running, or die/exit?

The lack of any messages suggests that the threads continue to run,
but file notifications never come in, which probably means we cannot
detect this problem automatically, and must rely on the users who know
which volumes can and cannot be supported.

Also, I presume that you tried to modify files on the mounted volumes,
while you had GDB attached to Emacs.  If not, please try modifying
files there, and see if that triggers any debug messages.

Thanks.





  parent reply	other threads:[~2013-01-24 18:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24  8:55 bug#13540: 24.3.50; Regression in trunk: auto-revert-mode fails on files accessed via samba Dani Moncayo
2013-01-24 10:13 ` Michael Albinus
2013-01-24 10:20   ` Dani Moncayo
2013-01-24 10:23     ` Michael Albinus
2013-01-24 16:22       ` Eli Zaretskii
2013-01-24 16:34         ` Dani Moncayo
2013-01-24 16:37           ` Dani Moncayo
2013-01-24 16:53           ` Eli Zaretskii
2013-01-24 17:23             ` Dani Moncayo
2013-01-24 17:28               ` Dani Moncayo
2013-01-24 17:39               ` Eli Zaretskii
2013-01-24 17:43               ` Eli Zaretskii
2013-01-24 17:44         ` Dani Moncayo
2013-01-24 18:13           ` Dani Moncayo
2013-01-24 18:29             ` Eli Zaretskii
2013-01-24 18:16           ` Eli Zaretskii [this message]
2013-01-25  7:46             ` Dani Moncayo
2013-01-25  7:57               ` Eli Zaretskii
2013-01-25  8:13                 ` Michael Albinus
2013-01-25  9:41                   ` Eli Zaretskii
2013-01-25  8:18                 ` Eli Zaretskii
2013-01-25  8:29                   ` Dani Moncayo
2013-01-25  9:27                     ` Eli Zaretskii
2013-01-25  9:34                       ` Dani Moncayo
2013-01-25 11:04                         ` Eli Zaretskii
2013-01-25 11:19                           ` Dani Moncayo
2013-01-25 13:44                             ` Eli Zaretskii
2013-01-25 13:29                           ` Michael Albinus
2013-02-14 10:09                             ` Michael Albinus
2013-01-24 16:32   ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83r4lala3q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13540@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --cc=michael.albinus@gmx.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).