unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "A.I." <merrick@luois.me>
Cc: Eli Zaretskii <eliz@gnu.org>, 54051@debbugs.gnu.org
Subject: bug#54051: 29.0.50; latest master build with lucid crashes
Date: Mon, 21 Feb 2022 18:09:27 +0800	[thread overview]
Message-ID: <87y224fs4o.fsf@yahoo.com> (raw)
In-Reply-To: <87a6ek3gsb.fsf@luois.me> (A. I.'s message of "Mon, 21 Feb 2022 13:51:38 +0800")

"A.I." <merrick@luois.me> writes:

> Hi,
>
> This is the backtrace I'm getting after compile emacs with
>
> ./configure --enable-checking='yes,glyphs' --enable-check-lisp-object-type --with-x-toolkit=lucid  CFLAGS='-O0 -g3'
>
> emacs started with gdb --args ./emacs -q -xrm 'Emacs.synchronous: true'

Thanks.

>           xconfigure = {
>             type = 22,
>             serial = 12048,
>             send_event = 1,
>             display = 0x55555609a920,
>             event = 83886802,
>             window = 83886802,
>             x = 0,
>             y = 0,
>             width = 0,
>             height = 0,
>             border_width = 0,
>             above = 0,
>             override_redirect = 0
>           },

This configure event is wrong: it specifies a width and height of zero,
which are invalid under X.  Then, the shell widget tries to reconfigure
its window to those invalid dimensions, which causes the crash.

The `send_event' field indicates that this event was sent by another
client and not the X server after window configuration (since we don't
send ConfigureNotify events to ourself anywhere in Emacs).

Please try to find the program that is sending these events.  It could
be a badly behaved window manager, for example.





  reply	other threads:[~2022-02-21 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  3:29 bug#54051: 29.0.50; latest master build with lucid crashes merrick--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-18  5:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-18  8:12 ` Eli Zaretskii
2022-02-18 12:42   ` A.I. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21  5:51     ` A.I. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 10:09       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-21 11:41         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-23  2:59           ` A.I. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-23  3:45             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87y224fs4o.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54051@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=merrick@luois.me \
    /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).