From: Live System User <nyc4bos@aol.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 29548@debbugs.gnu.org
Subject: bug#29548: 25.2; How to DEBUG get-device-terminal
Date: Sat, 06 Jan 2018 05:16:55 -0500 [thread overview]
Message-ID: <87zi5r5m20.fsf@aol.com> (raw)
In-Reply-To: <874lo1rr3n.fsf@users.sourceforge.net> (Noam Postavsky's message of "Thu, 04 Jan 2018 21:12:28 -0500")
Noam Postavsky <npostavs@users.sourceforge.net> writes:
> Live System User <nyc4bos@aol.com> writes:
>
>> Here's a new occurrance (see below):
>
> Hmm, if you can reproduce this semi-regularly, then perhaps the
> following patch can catch the reason for the problem. It sets a
> breakpoint in Fsignal while the terminal is in the process of being
> deleted (requires reproducing the problem under gdb with the patched
> .gdbinit loaded).
I applied your patch; thanks for it.
While playing around wirh the emacs daemon and TTY/GUI client frames,
I got a slightly diffent error message this time (I'lltry to see if
I can get back into the same exact situation/error message I got
before later...but here's this (perhaps?) slightly different one):
$ emacsclient -t file1.txt
*ERROR*: Terminal is not live, can’t create new frames on it
In the *server* buffer, I see:
server <127.0.0.1:60208>: Terminal is not live, can’t create new
frames on it
server <127.0.0.1:60208>: Status changed to closed: connection broken
by remote peer
server <127.0.0.1:60208>: server-delete-client
server <127.0.0.1:60208>: Deleted
(The screen quickly flashed the emacsclient frame and then it
disappered).
Your patch output displayed:
Breakpoint 3 at 0x508f7b: file terminal.c, line 317.
Breakpoint 4 at 0x508f91: file terminal.c, line 321.
(gdb) c
Continuing.
[New Thread 0x7fc3a0d25700 (LWP 7745)]
warning: the debug information found in "/usr/lib/debug//lib64/libfreebl3.so.debug" does not match "/lib64/libfreebl3.so" (CRC mismatch).
[New Thread 0x7fc39b162700 (LWP 7746)]
Thread 1 "emacs" hit Breakpoint 3, begin_delete_terminal () at terminal.c:317
317 delete_terminal_count++;
Thread 1 "emacs" hit Breakpoint 4, end_delete_terminal () at terminal.c:321
321 delete_terminal_count--;
Thread 1 "emacs" hit Breakpoint 3, begin_delete_terminal () at terminal.c:317
317 delete_terminal_count++;
Thread 1 "emacs" hit Breakpoint 4, end_delete_terminal () at terminal.c:321
321 delete_terminal_count--;
Thread 1 "emacs" hit Breakpoint 3, begin_delete_terminal () at terminal.c:317
317 delete_terminal_count++;
I noticed that this didn't end with a paired
"delete_terminal_count--;".
which it does do so normally.
After the initial error, the "delete_terminal_count" is no longer
displayed.
The *Messages* buffer contains multiple:
get-device-terminal: Invalid argument #<terminal 5> in
'get-device-terminal'
Error running timer battery-update-handler' (error Invalid argument
#<terminal 5> in 'get-device-terminal'")
whenever its timer goes off.
The "print_terminal_list" output was:
(gdb) print_terminal_list
$1 = {
header = {
size = 4611686018561773572
},
param_alist = 0,
charset_list = 0,
Vselection_alist = 0,
glyph_code_table = 0,
next_terminal = 0x0,
id = 0,
reference_count = 1,
type = output_initial,
name = 0xcaf940 "initial_terminal",
kboard = 0xce1fb0,
image_cache = 0x0,
display_info = {
tty = 0x0,
x = 0x0,
w32 = 0x0,
ns = 0x0
},
terminal_coding = 0xce8d70,
keyboard_coding = 0xce8b00,
---Type <return> to continue, or q <return> to quit---
rif = 0x0,
cursor_to_hook = 0x0,
raw_cursor_to_hook = 0x0,
clear_to_end_hook = 0x0,
clear_frame_hook = 0x0,
clear_end_of_line_hook = 0x0,
ins_del_lines_hook = 0x0,
insert_glyphs_hook = 0x0,
write_glyphs_hook = 0x0,
delete_glyphs_hook = 0x0,
ring_bell_hook = 0x0,
toggle_invisible_pointer_hook = 0x0,
reset_terminal_modes_hook = 0x0,
set_terminal_modes_hook = 0x0,
update_begin_hook = 0x0,
update_end_hook = 0x0,
set_terminal_window_hook = 0x0,
mouse_position_hook = 0x0,
frame_rehighlight_hook = 0x0,
frame_raise_lower_hook = 0x0,
fullscreen_hook = 0x0,
menu_show_hook = 0x0,
popup_dialog_hook = 0x0,
---Type <return> to continue, or q <return> to quit---
set_vertical_scroll_bar_hook = 0x0,
set_horizontal_scroll_bar_hook = 0x0,
condemn_scroll_bars_hook = 0x0,
redeem_scroll_bar_hook = 0x0,
judge_scroll_bars_hook = 0x0,
read_socket_hook = 0x0,
frame_up_to_date_hook = 0x0,
delete_frame_hook = 0x509839 <initial_free_frame_resources>,
delete_terminal_hook = 0x5098f4 <delete_initial_terminal>
}
(gdb)
Thanks.
next prev parent reply other threads:[~2018-01-06 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 15:42 bug#29548: 25.2; How to DEBUG get-device-terminal Live System User
2017-12-03 16:09 ` Noam Postavsky
2017-12-06 18:49 ` Live System User
2017-12-06 19:56 ` Noam Postavsky
2017-12-07 0:25 ` Live System User
2017-12-15 1:37 ` Noam Postavsky
2018-01-04 14:37 ` Live System User
2018-01-05 2:12 ` Noam Postavsky
2018-01-06 10:16 ` Live System User [this message]
2018-01-10 3:51 ` Noam Postavsky
2018-02-14 17:26 ` Live System User
2018-02-18 22:41 ` Noam Postavsky
2017-12-07 9:27 ` martin rudalics
2017-12-07 9:35 ` Noam Postavsky
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=87zi5r5m20.fsf@aol.com \
--to=nyc4bos@aol.com \
--cc=29548@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).