unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Damien Cassou <damien@cassou.me>
To: Eli Zaretskii <eliz@gnu.org>
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 12:33:51 +0100	[thread overview]
Message-ID: <87sgzll9ls.fsf@cassou.me> (raw)
In-Reply-To: <838t1dfs82.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:
>> (gdb) p data
>> $1 = XIL(0x1347253)

> Use "pp data" instead, it's better with conses, because it avoids the
> need to manually drill down into each cons cell.

(gdb) frame 10
#10 0x00000000005911d8 in cmd_error_internal (data=XIL(0x1347283), context=0x7fffffffce90 "") at keyboard.c:972
972	    call3 (Vcommand_error_function, data,

(gdb) pp data
(wrong-type-argument consp 
Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
0x00000000005870c8 in PSEUDOVECTOR_TYPE (v=0xc8c7000c8421c6c0) at lisp.h:1573
1573	  ptrdiff_t size = v->header.size;
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(safe_debug_print) will be abandoned.
When the function is done executing, GDB will silently stop.


-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill





  reply	other threads:[~2018-11-28 11:33 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
2018-11-28 11:33       ` Damien Cassou [this message]
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

  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=87sgzll9ls.fsf@cassou.me \
    --to=damien@cassou.me \
    --cc=33530@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --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 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).