From: Eli Zaretskii <eliz@gnu.org>
To: Damien Cassou <damien@cassou.me>
Cc: 33530@debbugs.gnu.org, eggert@cs.ucla.edu, michael.albinus@gmx.de
Subject: bug#33530: 26.1.90; D-Bus crashes Emacs: consp, Fatal error 7: Bus error
Date: Wed, 28 Nov 2018 11:48:13 +0200 [thread overview]
Message-ID: <838t1dfs82.fsf@gnu.org> (raw)
In-Reply-To: <87k1kx1rg0.fsf@cassou.me> (message from Damien Cassou on Wed, 28 Nov 2018 10:28:47 +0100)
> From: Damien Cassou <damien@cassou.me>
> Cc: 33530@debbugs.gnu.org, eggert@cs.ucla.edu, michael.albinus@gmx.de
> Date: Wed, 28 Nov 2018 10:28:47 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
> > Can you please show the value of 'data' in frame #10 or in frame #5,
> > in human-readable form? This should be possible using the "xtype"
> > command followed by another x* command, according to what type is
> > shown by "xtype", probably "xsymbol".
>
> I would like to do that but I lack knowledge of gdb. Here is what I came
> up with:
>
> (gdb) frame 10
> #10 0x00000000005911d8 in cmd_error_internal (data=XIL(0x1347253), context=0x7fffffffce90 "") at keyboard.c:972
> 972 call3 (Vcommand_error_function, data,
>
> (gdb) p data
> $1 = XIL(0x1347253)
>
> (gdb) xtype
> Lisp_Cons
>
> (gdb) xcons
Use "pp data" instead, it's better with conses, because it avoids the
need to manually drill down into each cons cell.
Thanks.
next prev parent reply other threads:[~2018-11-28 9:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 20:59 bug#33530: 26.1.90; D-Bus crashes Emacs: consp, Fatal error 7: Bus error Damien Cassou
2018-11-28 5:40 ` Paul Eggert
2018-11-28 7:10 ` Eli Zaretskii
2018-11-28 9:36 ` Damien Cassou
2018-11-28 6:16 ` Eli Zaretskii
2018-11-28 9:28 ` Damien Cassou
2018-11-28 9:48 ` Eli Zaretskii [this message]
2018-11-28 11:33 ` Damien Cassou
2018-11-28 12:00 ` Eli Zaretskii
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=838t1dfs82.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33530@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=eggert@cs.ucla.edu \
--cc=michael.albinus@gmx.de \
/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.