From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21337@debbugs.gnu.org
Subject: bug#21337: 25.0.50; inotify error message
Date: Mon, 24 Aug 2015 18:51:38 +0200 [thread overview]
Message-ID: <87twrobpet.fsf@gmail.com> (raw)
In-Reply-To: <83a8tghcgr.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Aug 2015 19:34:44 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> '(dired-auto-revert-buffer (quote dired-directory-changed-p))
>> '(global-auto-revert-mode t)
>> '(global-auto-revert-non-file-buffers t)
>>
>> although disabling those 3 makes no difference to the behaviour.
>
> Then I guess the next step is to set debug-on-error non-nil and show
> the backtrace, so that we see what Lisp code errors out.
>
I hadn't considered that, however it's not very enlightening:
Debugger entered--Lisp error: (file-notify-error "Error while trying to read file system events")
That error is coming from the inotify_callback function. From gdb the
c-backtrace is:
#0 inotify_callback (fd=16, _=<optimized out>) at inotify.c:139
#1 0x000000000059e3a0 in wait_reading_process_output (time_limit=<optimized out>, nsecs=<optimized out>, read_kbd=-1,
do_display=true, wait_for_cell=0, wait_proc=0x0, just_wait_proc=0) at process.c:5085
#2 0x0000000000422672 in sit_for (timeout=30, reading=112, display_option=0) at dispnew.c:5756
#3 0x00000000004fa6dd in read_char (commandflag=0, commandflag@entry=1, map=13674864, map@entry=99582755, prev_event=-11,
used_mouse_menu=0xfffffffffffffea8, used_mouse_menu@entry=0x7fffffffd7db, end_time=0xd0a990, end_time@entry=0x0)
at keyboard.c:2786
#4 0x00000000004fb469 in read_key_sequence (keybuf=keybuf@entry=0x7fffffffd8b0, prompt=prompt@entry=0,
dont_downcase_last=dont_downcase_last@entry=false, can_return_switch_frame=can_return_switch_frame@entry=true,
fix_current_buffer=fix_current_buffer@entry=true, prevent_redisplay=prevent_redisplay@entry=false, bufsize=30) at keyboard.c:9188
#5 0x00000000004fd171 in command_loop_1 () at keyboard.c:1406
#6 0x000000000055fbd7 in internal_condition_case (bfun=bfun@entry=0x4fcf30 <command_loop_1>, handlers=handlers@entry=18912,
hfun=hfun@entry=0x4f3a30 <cmd_error>) at eval.c:1356
#7 0x00000000004ef00c in command_loop_2 (ignore=ignore@entry=0) at keyboard.c:1138
#8 0x000000000055fab3 in internal_catch (tag=tag@entry=45168, func=func@entry=0x4eeff0 <command_loop_2>, arg=arg@entry=0)
at eval.c:1116
#9 0x00000000004eefc9 in command_loop () at keyboard.c:1117
#10 0x00000000004f363b in recursive_edit_1 () at keyboard.c:723
#11 0x00000000004f3960 in Frecursive_edit () at keyboard.c:794
#12 0x00000000004187d6 in main (argc=1, argv=0x7fffffffdc38) at emacs.c:1629
xbacktrace gives no output at all.
printf time?
Regards
Robert
next prev parent reply other threads:[~2015-08-24 16:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 12:12 bug#21337: 25.0.50; inotify error message Robert Pluim
2015-08-24 15:52 ` Eli Zaretskii
2015-08-24 16:22 ` Robert Pluim
2015-08-24 16:34 ` Eli Zaretskii
2015-08-24 16:51 ` Robert Pluim [this message]
2015-08-24 17:18 ` Eli Zaretskii
2015-08-24 18:32 ` Robert Pluim
2015-08-24 19:36 ` Eli Zaretskii
2015-08-26 17:02 ` Robert Pluim
2015-08-28 13:30 ` Eli Zaretskii
2015-09-05 8:38 ` Eli Zaretskii
2015-09-07 7:21 ` Tassilo Horn
2015-09-07 7:43 ` Robert Pluim
2015-09-07 15:01 ` Eli Zaretskii
2015-09-07 15:15 ` Robert Pluim
2015-09-09 16:49 ` Tassilo Horn
2015-09-09 17:57 ` 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=87twrobpet.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=21337@debbugs.gnu.org \
--cc=eliz@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 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).