From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 21313@debbugs.gnu.org
Subject: bug#21313: 25.0.50; Strange errors from dbus-handle-event
Date: Fri, 11 Sep 2015 16:59:33 +0300 [thread overview]
Message-ID: <83wpvx2h16.fsf@gnu.org> (raw)
In-Reply-To: <871te5cdg7.fsf@gnu.org>
> From: Tassilo Horn <tsdh@gnu.org>
> Cc: 21313@debbugs.gnu.org
> Date: Fri, 11 Sep 2015 15:06:48 +0200
>
> > So I suggest to read the description of the root cause posted by
> > Robert Pluim in http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21337#31,
> > and then look for something very similar, but involving other sources
> > of input events, perhaps D-Bus. The symptoms you describe exactly
> > match what he explained there.
>
> The problem is that I have almost no idea what that code does and how it
> is intended to work, so I can't really debug it in a sensible way.
You mean, wait_reading_process_output? Please feel free to ask
questions about the things you don't understand.
In a nutshell, it waits until one of the input sources has some input,
and then we read from that source using whatever method is appropriate
for interpreting that source.
> If you have some ideas where things could go wrong, I'm happy to do
> whatever may help.
I think things go wrong exactly like in that other bug: we have some
source ready to be read from, but dispatch those events to a "handler"
for another source.
> Maybe adding some debugging code or conditional breakpoints could
> narrow down the scope a bit?
I'd start by looking at the indicators returned by 'pselect'.
> BTW, the last errors came from `file-notify-handle-event' but I'm
> reasonably sure that in this emacs session I only had used Gnus so far.
> I don't use auto-revert-mode, so actually filenotify.el should not even
> have been loaded so far and no watches should have existed. My current
> emacs session is the same: only Gnus => (featurep 'filenotify) ;=> nil.
> Does that give any clue?
My theory is that we think there's an inotify event waiting to be
read, where in fact the event is of another kind, perhaps from D-Bus.
The flags returned by 'pselect' should tell you.
next prev parent reply other threads:[~2015-09-11 13:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 16:24 bug#21313: 25.0.50; Strange errors from dbus-handle-event Tassilo Horn
2015-09-09 20:43 ` Tassilo Horn
2015-09-11 12:28 ` Tassilo Horn
2015-09-11 12:39 ` Eli Zaretskii
2015-09-11 13:06 ` Tassilo Horn
2015-09-11 13:59 ` Eli Zaretskii [this message]
2015-09-15 15:37 ` Tassilo Horn
2015-09-15 16:01 ` Eli Zaretskii
2015-09-16 11:39 ` Tassilo Horn
2015-09-22 5:49 ` Tassilo Horn
2015-09-22 8:00 ` Robert Pluim
2015-09-22 8:21 ` Tassilo Horn
2015-10-02 18:36 ` Tassilo Horn
2015-10-02 19:05 ` Eli Zaretskii
2015-10-02 20:33 ` Tassilo Horn
2015-10-02 21:10 ` Eli Zaretskii
2015-10-02 21:26 ` Michael Albinus
2015-10-03 5:40 ` Tassilo Horn
2015-10-03 6:32 ` Tassilo Horn
2015-10-03 7:14 ` Eli Zaretskii
2015-10-03 8:10 ` Tassilo Horn
2015-10-03 9:53 ` Eli Zaretskii
2015-10-03 12:06 ` Tassilo Horn
2015-10-03 7:43 ` Michael Albinus
2015-10-03 8:13 ` Tassilo Horn
2015-10-03 9:38 ` Tassilo Horn
2015-10-03 10:53 ` Eli Zaretskii
2015-10-14 9:58 ` Tassilo Horn
2015-10-14 17:05 ` Eli Zaretskii
2015-10-14 19:37 ` Tassilo Horn
2015-10-14 19:43 ` Eli Zaretskii
2015-10-15 11:37 ` Tassilo Horn
2015-10-15 16:56 ` Eli Zaretskii
2015-10-15 17:35 ` Tassilo Horn
2015-10-15 19:44 ` Eli Zaretskii
2015-10-16 4:53 ` Tassilo Horn
2015-10-16 7:02 ` Eli Zaretskii
2015-10-16 7:45 ` Tassilo Horn
2015-10-16 8:23 ` Eli Zaretskii
2015-10-16 9:25 ` Tassilo Horn
2015-10-16 10:11 ` Eli Zaretskii
2015-10-16 10:22 ` Tassilo Horn
2015-10-29 7:43 ` Tassilo Horn
2015-10-29 16:19 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wpvx2h16.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21313@debbugs.gnu.org \
--cc=tsdh@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.