all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kun Liu <kun.liu@gmail.com>
Cc: 70760@debbugs.gnu.org
Subject: bug#70760: 29.3.50; core dumps when copy in other apps
Date: Sat, 04 May 2024 22:02:32 +0300	[thread overview]
Message-ID: <86zft5e6yf.fsf@gnu.org> (raw)
In-Reply-To: <CA+Nei8PO8YhGCpOcyksgGcP3RU1VbjAH5s7VB4L_d2uhVxe0iQ@mail.gmail.com> (message from Kun Liu on Sat, 4 May 2024 11:08:31 -0700)

> From: Kun Liu <kun.liu@gmail.com>
> Date: Sat, 4 May 2024 11:08:31 -0700
> Cc: 70760@debbugs.gnu.org
> 
> (gdb) xtype data
> Lisp_Cons
> (gdb) xcar data
> $2 = 0x11f40
> (gdb) xcdr data
> $3 = 0x0
> (gdb) xstring data
> $4 = (struct Lisp_String *) 0x0
> "DEAD"

This is not how you explore a cons cell in GDB.  The correct sequence
is:

  (gdb) print data
  (gdb) xtype

If "xtype" says it's a cons cell, the next command should be "xcar",
followed by "xtype", to show the type of car.  If "xtype" says it's a
symbol, the next command should be "xsymbol", to show the symbol's
name.  Once you are done with car, continue to cdr, like this:

  (gdb) print data
  (gdb) xcdr
  (gdb) xtype

Then again use the appropriate command given what "xtype" says.  Etc.,
etc.

Also, do you remember what you did in Emacs when it crashed?  Was it
C-y or something similar?





  reply	other threads:[~2024-05-04 19:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 21:30 bug#70760: 29.3.50; core dumps when copy in other apps Kun Liu
2024-05-04  7:11 ` Eli Zaretskii
2024-05-04 18:08   ` Kun Liu
2024-05-04 19:02     ` Eli Zaretskii [this message]
     [not found]       ` <CA+Nei8PsdEL-bOOQg86aZk1n1ahpb38XUokyHR98muaRTUY+5Q@mail.gmail.com>
2024-05-04 21:37         ` Kun Liu
2024-05-05  5:11         ` Eli Zaretskii
2024-05-05 15:45           ` Kun Liu
2024-05-05 16:12             ` Eli Zaretskii
2024-05-05 16:44               ` Kun Liu
2024-05-05 17:11                 ` Kun Liu
2024-05-05 17:34               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-14  6:17                 ` Kun Liu
2024-05-14  7:13                   ` Eli Zaretskii
2024-05-15 10:35                     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 16:27                       ` Kun Liu
2024-05-15 17:54                         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 18:25                           ` Kun Liu
2024-05-15 21:06                             ` Kun Liu
2024-05-16  9:20                               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-16 19:07                                 ` Kun Liu
2024-05-17 16:23                                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 17:34                                     ` Eli Zaretskii
2024-05-17 20:43                                       ` Kun Liu
2024-05-18  0:34                                         ` Kun Liu
2024-05-18 10:32                                       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 11:44                                         ` Eli Zaretskii
2024-05-18 11:54                                           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 12:09                                             ` Eli Zaretskii
2024-05-18 16:55                                               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 17:54                                                 ` Eli Zaretskii
2024-05-18 18:22                                                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 19:20                                                     ` Eli Zaretskii
2024-05-16  9:07                             ` Michael Albinus 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86zft5e6yf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70760@debbugs.gnu.org \
    --cc=kun.liu@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 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.