unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Van Ly via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rudalics@gmx.at, 74496@debbugs.gnu.org
Subject: bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts
Date: Wed, 04 Dec 2024 05:15:21 +0000	[thread overview]
Message-ID: <dcsa5dc58ra.fsf@SDF.ORG> (raw)
In-Reply-To: <86v7w22gyd.fsf@gnu.org> (message from Eli Zaretskii on Mon, 02 Dec 2024 18:22:02 +0200)


Eli Zaretskii <eliz@gnu.org> writes:

>>   i.  start, emacs -Q
>>   ii. use, M-x gdb
>> 
>
> At this point, you should see a prompt in the minibuffer saysing
> something like
>
>  Run gdb (like this): gdb -i=mi SOMETHING
>
> Edit the last part so it says /path/to/emacs instead of SOMETHING, and
> then press RET.
>

Thanks, having the path to emacs will let gdb run.

  33  (gdb) condition 1 lval == Qnil
  34  No symbol "builtin_lisp_symbol" in current context.

What more is needed for a watch at the break conditional on `lval == Qnil'?

   1  For help, type "help".
   2  Type "apropos word" to search for commands related to "word"...
   3  Reading symbols from /src/emacs/build-30-1/src/emacs...
   4  warning: File "/src/emacs/build-30-1/src/.gdbinit" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
   5  To enable execution of this file add
   6  	add-auto-load-safe-path /src/emacs/build-30-1/src/.gdbinit
   7  line to your configuration file "/u/xxx/.gdbinit".
   8  To completely disable this security protection add
   9  	set auto-load safe-path /
  10  line to your configuration file "/u/xxx/.gdbinit".
  11  For more information about this security protection see the
  12  "Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
  13  	info "(gdb)Auto-loading safe path"
  14  (gdb) break xterm.c:18044 if lval == Qnil
  15  No symbol "builtin_lisp_symbol" in current context.
  16  (gdb) break xterm.c:28275 if lval == Qnil
  17  No symbol "builtin_lisp_symbol" in current context.
  18  (gdb) break xterm.c:28275 if lval == Qnil
  19  No symbol "builtin_lisp_symbol" in current context.
  20  (gdb) info b
  21  No breakpoints or watchpoints.
  22  (gdb) break xterm.c:18044 
  23  Breakpoint 1 at 0x4d048c: file /src/emacs/30.0.91/src/xterm.c, line 18044.
  24  (gdb) break xterm.c:28275
  25  Breakpoint 2 at 0x4d03c7: file /src/emacs/30.0.91/src/xterm.c, line 28275.
  26  (gdb) break xterm.c:28343
  27  Breakpoint 3 at 0x4e640b: file /src/emacs/30.0.91/src/xterm.c, line 28343.
  28  (gdb) info b
  29  Num     Type           Disp Enb Address            What
  30  1       breakpoint     keep y   0x00000000004d048c in x_net_wm_state at /src/emacs/30.0.91/src/xterm.c:18044
  31  2       breakpoint     keep y   0x00000000004d03c7 in x_handle_net_wm_state at /src/emacs/30.0.91/src/xterm.c:28275
  32  3       breakpoint     keep y   0x00000000004e640b in x_check_fullscreen at /src/emacs/30.0.91/src/xterm.c:28343



-- 
vl





  reply	other threads:[~2024-12-04  5:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-23 18:28 bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 10:23 ` Eli Zaretskii
2024-11-30 10:36   ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 13:03     ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 16:53       ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 18:21         ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 19:01           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 19:25             ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01  8:46               ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01  9:59                 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 11:05                   ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 14:26                     ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 17:50                       ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-02 16:04                         ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-03  8:24                           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-04  5:58                             ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-04  9:53                               ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-02 15:47                     ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-02 16:22                       ` Eli Zaretskii
2024-12-04  5:15                         ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-04  9:52                           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-03  8:24                       ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-04  5:47                         ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-04  9:53                           ` martin rudalics 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=dcsa5dc58ra.fsf@SDF.ORG \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74496@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rudalics@gmx.at \
    --cc=van.ly@SDF.ORG \
    /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).