From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Mike Kupfer <kupfer@rawbw.com>
Cc: Feng Shu <tumashu@163.com>,
Stephen Berman <stephen.berman@gmx.net>,
58771@debbugs.gnu.org, Visuwesh <visuweshm@gmail.com>
Subject: bug#58771: 29.0.50; context submenu can not click when run emacs lucid build.
Date: Wed, 11 Jan 2023 17:47:18 +0800 [thread overview]
Message-ID: <87ilhdflnd.fsf@yahoo.com> (raw)
In-Reply-To: <88623.1673420245@alto> (Mike Kupfer's message of "Tue, 10 Jan 2023 22:57:25 -0800")
Mike Kupfer <kupfer@rawbw.com> writes:
> I don't even need to rerun configure. I just added a debug fprintf to
> pop_up_menu(), rebuilt Emacs, and the problem vanished.
Would you please send me the two different binaries?
(Off-list, please, if you're worried about the binaries containing
private information.)
> I still have the binary that fails. On a hunch, I added a breakpoint at
> the start of pop_up_menu(). When the breakpoint triggered, I checked
> the value of lucid__menu_grab_keyboard. gdb says
>
> (gdb) print lucid__menu_grab_keyboard
> $2 = false
>
> Yet *Help* says that the value of lucid--menu_grab_keyboard is t.
>
> If I do
>
> M-: (setq lucid--menu_grab_keyboard t)
>
> and press F10, gdb says lucid__menu_grab_keyboard is still false.
>
> I did a little more poking around with gdb and found that
> lucid__menu_grab_keyboard moves around inside "globals".
>
> Broken binary:
>
> (gdb) print &globals.f_lucid__menu_grab_keyboard
> $3 = (_Bool *) 0x555555d54a98 <globals+4152>
>
> Working binary:
>
> (gdb) print &globals.f_lucid__menu_grab_keyboard
> $2 = (_Bool *) 0x555555d54ad0 <globals+4208>
>
> This strikes me as more than a little odd. Given that all I did was
> add a couple fprintfs, I'd expect the layout of "globals" to stay the
> same.
I have a hunch. If you touch globals.h in src, does it result in files
under the lwlib directory being rebuilt?
My guess is globals.h changed but lwlib was not incrementally rebuilt.
I guess this means lwlib/*.o has to be made to depend on
$(top_builddir)/globals.stamp or somesuch. Thanks.
next prev parent reply other threads:[~2023-01-11 9:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 5:28 bug#58771: 29.0.50; context submenu can not click when run emacs lucid build Feng Shu
2022-10-25 7:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 8:35 ` Feng Shu
2022-10-25 10:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 13:58 ` Stephen Berman
2022-10-26 0:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 8:00 ` Stephen Berman
2022-10-26 8:18 ` Visuwesh
2022-10-26 9:40 ` Stephen Berman
2023-01-11 6:57 ` Mike Kupfer
2023-01-11 9:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-01-11 20:44 ` Mike Kupfer
2023-01-12 1:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-12 2:16 ` Mike Kupfer
2023-01-12 3:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-12 8:05 ` Eli Zaretskii
2023-01-12 10:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-13 2:43 ` Mike Kupfer
2023-01-13 7:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-13 7:32 ` Eli Zaretskii
2023-01-14 2:28 ` Paul Eggert
2023-01-14 7:25 ` Eli Zaretskii
2023-01-14 7:48 ` Paul Eggert
2023-01-13 7:35 ` Jean Louis
2023-01-12 8:56 ` Eli Zaretskii
2023-01-13 5:23 ` Mike Kupfer
2022-10-26 8:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 9:40 ` Stephen Berman
2022-10-26 9:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 2:14 ` Feng Shu
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=87ilhdflnd.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=58771@debbugs.gnu.org \
--cc=kupfer@rawbw.com \
--cc=luangruo@yahoo.com \
--cc=stephen.berman@gmx.net \
--cc=tumashu@163.com \
--cc=visuweshm@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 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.