GNU bug report logs - #75318
Lisp_Subr header and layout

Previous Next

Package: emacs;

Reported by: Pip Cet <pipcet <at> protonmail.com>

Date: Fri, 3 Jan 2025 14:31:02 UTC

Severity: normal

Full log


View this message in rfc822 format

From: Pip Cet <pipcet <at> protonmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: luangruo <at> yahoo.com, monnier <at> iro.umontreal.ca, 75318 <at> debbugs.gnu.org
Subject: bug#75318: Lisp_Subr header and layout
Date: Wed, 22 Jan 2025 17:57:48 +0000
"Eli Zaretskii" <eliz <at> gnu.org> writes:

>> Date: Wed, 22 Jan 2025 16:07:52 +0000
>> From: Pip Cet <pipcet <at> protonmail.com>
>> Cc: 75318 <at> debbugs.gnu.org, luangruo <at> yahoo.com, monnier <at> iro.umontreal.ca
>>
>> (In GDB, with .gdbinit loaded, "p LISPSYM_INITIALLY (Qnil)" prints an
>> unhelpful "{0x0}"; "p lisp_h_Qnil" prints "{0}".  ptype thinks the first
>> is a Lisp_Object (but expands the type to its obscure definition), the
>> second claims to be a singleton array of int.
>
> I guess your build is with check-lisp-objects?  Because here I get

Sorry, meant to mention that and forgot.  It is.

>   (gdb) p LISPSYM_INITIALLY (Qnil)
>   $1 = 0
>   (gdb) p lisp_h_Qnil
>   $3 = 0
>   (gdb) ptype LISPSYM_INITIALLY(Qnil)
>   type = long long
>   (gdb) ptype lisp_h_Qnil
>   type = int

I guess your build is with wide Emacs ints, as usual :-)

I'd also forgotten about "whatis", which splits the difference and tells
me the first is a Lisp_Word, not a Lisp_Object.

Pip





This bug report was last modified 144 days ago.

Previous Next


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