unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Van Ly <van.ly@SDF.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: Mon, 02 Dec 2024 18:22:02 +0200	[thread overview]
Message-ID: <86v7w22gyd.fsf@gnu.org> (raw)
In-Reply-To: <dcs7c8inl2g.fsf@SDF.ORG> (message from Van Ly on Mon, 02 Dec 2024 15:47:35 +0000)

> From: Van Ly <van.ly@SDF.ORG>
> Cc: eliz@gnu.org, 74496@debbugs.gnu.org
> Date: Mon, 02 Dec 2024 15:47:35 +0000
> 
> I pieced together the following steps to make emacs debuggable.  I'll
> need pointers to info pages to make progress.
> 
> 
> 
>   a.  make distclean
>   b.  configure ... 'CFLAGS=-g3 -ggdb -Og ...'
>   c.  make
> 
> 
> 
>   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.

>    1  For help, type "help".
>    2  Type "apropos word" to search for commands related to "word"...
>    3  "0x7f7fff604da0s": not in executable format: file format not recognized
>    4  No symbol table is loaded.  Use the "file" command.
>    5  Breakpoint 1 (xterm.c:18044) pending.
>    6  No symbol table is loaded.  Use the "file" command.
>    7  Breakpoint 2 (xterm.c:28275) pending.
>    8  No symbol table is loaded.  Use the "file" command.
>    9  Breakpoint 3 (xterm.c:28343) pending.
>   10  (gdb) run
>   11  The target does not support running in non-stop mode.

This is because you didn't give GDB the executable (emacs) to work on
and run.  If you do it like above, then "run" should start Emacs.






      reply	other threads:[~2024-12-02 16:22 UTC|newest]

Thread overview: 16+ 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-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 [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

  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=86v7w22gyd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74496@debbugs.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).