From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 30019@debbugs.gnu.org
Subject: bug#30019: 26.0.90; Invalid specification of parent-frame with desktop-read
Date: Tue, 09 Jan 2018 20:40:14 +0200 [thread overview]
Message-ID: <83zi5m6fld.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48zeXy1OzYEmiZh4mNuaEFQsGCRRObbih0Nr4VAXXBpUdg@mail.gmail.com> (message from Aaron Jensen on Tue, 9 Jan 2018 08:21:57 -0800)
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Tue, 9 Jan 2018 08:21:57 -0800
>
> Btw, is there a guide to setting a breakpoint in C code for emacs
> source?
You mean, how to use GDB? You'd need to read the GDB manual. The
command is "break". In this case, I'd set a breakpoint at entry to
x_set_parent_frame:
(gdb) break x_set_parent_frame
and when it breaks, do this:
(gdb) p f->output_method
If the result is not output_x_window, then FRAME_X_P would yield
zero, because it's definition is
#define FRAME_X_P(f) ((f)->output_method == output_x_window)
There's some advice on debugging Emacs in etc/DEBUG, but it doesn't
teach you basic GDB.
next prev parent reply other threads:[~2018-01-09 18:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 2:48 bug#30019: 26.0.90; Invalid specification of parent-frame with desktop-read Aaron Jensen
2018-01-08 9:53 ` martin rudalics
2018-01-09 10:24 ` martin rudalics
2018-01-09 16:21 ` Aaron Jensen
2018-01-09 18:40 ` Eli Zaretskii [this message]
2018-01-10 10:20 ` martin rudalics
2018-01-10 15:53 ` Eli Zaretskii
2018-01-11 10:54 ` martin rudalics
2018-01-11 16:07 ` Eli Zaretskii
2018-01-11 17:06 ` martin rudalics
2018-01-11 17:56 ` Eli Zaretskii
2018-01-11 18:20 ` martin rudalics
2018-01-11 20:49 ` Eli Zaretskii
2018-01-12 8:47 ` martin rudalics
2018-01-12 9:43 ` Eli Zaretskii
2018-01-13 2:42 ` Aaron Jensen
2018-01-13 8:50 ` martin rudalics
2020-08-26 13:26 ` Lars Ingebrigtsen
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=83zi5m6fld.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30019@debbugs.gnu.org \
--cc=aaronjensen@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 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).