From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 59480@debbugs.gnu.org
Subject: bug#59480: 29.0.50; emacs master with --enable-checking fails assert in x_display_set_last_user_time
Date: Tue, 22 Nov 2022 20:56:10 +0800 [thread overview]
Message-ID: <87bkoz407p.fsf@yahoo.com> (raw)
In-Reply-To: <87o7sz9o6e.fsf@gmail.com> (Robert Pluim's message of "Tue, 22 Nov 2022 13:19:37 +0100")
Robert Pluim <rpluim@gmail.com> writes:
> This is master as of right now, configured with:
>
> ./configure --enable-checking=yes,glyphs
>
> src/emacs -Q
>
> xterm.c:7753: Emacs fatal error: assertion failed: time <= X_ULONG_MAX
>
> Thread 1 "emacs" hit Breakpoint 1, terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:426
> 426 signal (sig, SIG_DFL);
> (gdb) bt
> #0 terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:426
> #1 0x00005555555b3320 in die (msg=<optimized out>, file=<optimized out>, line=<optimized out>) at alloc.c:7697
> #2 0x00005555556d4d47 in x_display_set_last_user_time (dpyinfo=0x5555562ec000, time=18446744071827324120, send_event=true, set_property=true) at xterm.c:7753
> #3 0x00005555556ea241 in handle_one_xevent (dpyinfo=0x5555562ec000, event=0x7fffffffd490, finish=0x555555eebd24 <current_finish>, hold_quit=0x7fffffffd730) at xterm.c:18624
> #4 0x00005555556e77ac in event_handler_gdk (gxev=0x7fffffffd490, ev=0x5555560a33c0, data=0x0) at xterm.c:17412
>
> (gdb) up
> #6 0x00005555556d4d47 in x_display_set_last_user_time (dpyinfo=0x5555562ec000, time=18446744071827324120, send_event=true, set_property=true) at xterm.c:7753
>
> 7753 eassert (time <= X_ULONG_MAX);
> (gdb) up
> #7 0x00005555556ea241 in handle_one_xevent (dpyinfo=0x5555562ec000, event=0x7fffffffd490, finish=0x555555eebd24 <current_finish>, hold_quit=0x7fffffffd730) at xterm.c:18624
> 18624 x_display_set_last_user_time (dpyinfo, event->xclient.data.l[1],
> (gdb) p X_ULONG_MAX
> $1 = 4294967295
>
> X_ULONG_MAX looks very 32bit-ish :-)
>
> (why this started happening just now I donʼt know, that assert has
> been in for ages)
>
> Robert
Thanks, should be fixed now.
next prev parent reply other threads:[~2022-11-22 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 12:19 bug#59480: 29.0.50; emacs master with --enable-checking fails assert in x_display_set_last_user_time Robert Pluim
2022-11-22 12:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-22 13:12 ` Robert Pluim
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=87bkoz407p.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=59480@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=rpluim@gmail.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: 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).