From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Madhu <enometh@meer.net>
Cc: 59733@debbugs.gnu.org
Subject: bug#59733: 29.0.50; unresponsive Xaw menus
Date: Mon, 05 Dec 2022 16:58:13 +0800 [thread overview]
Message-ID: <878rjmp6qi.fsf@yahoo.com> (raw)
In-Reply-To: <20221205.133509.1828285180404809868.enometh@meer.net> (Madhu's message of "Mon, 05 Dec 2022 13:35:09 +0530 (IST)")
Madhu <enometh@meer.net> writes:
> Thanks, unfortunately this looks like a genuine heisenbug and my
> earlier reports should be deemed unreliable. I do have builds which
> "don't work" but I'm am now unable to produce *new* builds which
> "don't work", (say with adding printf debugging or resetting)
>
> AFAICT both XtGrabPointer and XtGrabKeyboard return Success in all
> cases (both "works" and "doesn't work" builds) - keyboard and pointer
> are both grabbed as expected - from gdb dprintfs, disassembly seems
> identical.
>
> The only significant thing I can report (I have libinput
> enable-tab=true) on a "doesn't work" build is that if i quickly make
> two single taps on the help button on the toolbar, on the touchpad,
> then the pop-up-menu "works". (the effect seems to be an event
> between the activation of the menu and the display of the menu - F10
> doesn't work as usual). There hasn't been any progress Sorry
This might be a stab in the dark, but:
Can you run both builds that "work" and those that "don't work" under
Valgrind and see if there is some memory problem causing this?
Make sure to run Emacs with "--eval (setq gc-cons-threshold
most-positive-fixnum)" specified on the command line, or false positives
will be reported during GC.
prev parent reply other threads:[~2022-12-05 8:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 2:35 bug#59733: 29.0.50; unrespnsive Xaw menus Madhu
2022-12-01 7:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01 9:34 ` Madhu
2022-12-01 10:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01 12:56 ` Madhu
2022-12-01 13:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01 13:55 ` Visuwesh
2022-12-01 14:24 ` Madhu
2022-12-02 1:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 5:24 ` Madhu
2022-12-04 6:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05 8:05 ` bug#59733: 29.0.50; unresponsive " Madhu
2022-12-05 8:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=878rjmp6qi.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=59733@debbugs.gnu.org \
--cc=enometh@meer.net \
--cc=luangruo@yahoo.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 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.