GNU bug report logs - #70760
29.3.50; core dumps when copy in other apps

Previous Next

Full log

View this message in rfc822 format

From: Kun Liu <kun.liu <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>, 70760 <at> debbugs.gnu.org
Subject: bug#70760: 29.3.50; core dumps when copy in other apps
Date: Sat, 4 May 2024 14:37:43 -0700

[Message part 1 (text/plain, inline)]

+  70760 <at> debbugs.gnu.org

On Sat, May 4, 2024 at 1:49 PM Kun Liu <kun.liu <at> gmail.com> wrote:

> Thank you, Eli.
>
> Here is the result.
>
> (gdb) print data
> $1 = XIL(0x55f268372323)
> (gdb) xtype
> Lisp_Cons
> (gdb) xcar
> $2 = 0x11f40
> (gdb) xtype
> Lisp_Symbol
> (gdb) xsymbol
> $3 = (struct Lisp_Symbol *) 0x55f2626ad440 <lispsym+73536>
> "wrong-type-argument"
>
> To your question, I wasn't doing anything in Emacs. I was just copying in
> Chrome.
>
> Also I upgraded VirtualBox from 6 to 7. And looks like Emacs is no longer
> crashing. Now it reports the following in mini-bufffer:
>
> funcall-interactively: Wrong type argument: listp, [(2 19 1) ((emacs
> (24))) "A modern list library for Emacs" tar ((:commit .
> "39d067b9fbb2db65fc7a6938bfb21489ad990cb4") (:authors ("Magnar Sveen" . "
> magnars <at> gmail.com")) (:maintainers ("Magnar Sveen" . "magnars <at> gmail.com"))
> (:maintainer "Magnar Sveen" . "magnars <at> gmail.com") (:keywords
> "extensions" "lisp") (:url . "https://github.com/magnars/dash.el"))]
>
> On Sat, May 4, 2024 at 12:02 PM Eli Zaretskii <eliz <at> gnu.org> wrote:
>
>> > From: Kun Liu <kun.liu <at> gmail.com>
>> > Date: Sat, 4 May 2024 11:08:31 -0700
>> > Cc: 70760 <at> 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?
>>
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.