emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#53058: closed (etc/DEBUG could say more about --enable-check-lisp-ob


From: GNU bug Tracking System
Subject: bug#53058: closed (etc/DEBUG could say more about --enable-check-lisp-object-type)
Date: Thu, 03 Feb 2022 07:29:02 +0000

Your message dated Thu, 03 Feb 2022 09:28:49 +0200
with message-id <83h79g5rym.fsf@gnu.org>
and subject line Re: bug#53058: etc/DEBUG could say more about 
--enable-check-lisp-object-type
has caused the debbugs.gnu.org bug report #53058,
regarding etc/DEBUG could say more about --enable-check-lisp-object-type
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
53058: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53058
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: etc/DEBUG could say more about --enable-check-lisp-object-type Date: Thu, 06 Jan 2022 11:20:19 -0700 User-agent: Notmuch/0.31.4 (https://notmuchmail.org) Emacs/29.0.50 (x86_64-pc-linux-gnu)
Hello,

On Wed 05 Jan 2022 at 02:11PM +02, Eli Zaretskii wrote:

> Comparisons with structures, like foo == Qnil, aren't guaranteed to
> work in GDB.  --enable-check-lisp-object-type makes Lisp objects be
> structures rather than simple scalar values.

Thanks -- how about the attached?

-- 
Sean Whitton

Attachment: 0001-etc-DEBUG-Say-more-about-enable-check-lisp-object-ty.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: bug#53058: etc/DEBUG could say more about --enable-check-lisp-object-type Date: Thu, 03 Feb 2022 09:28:49 +0200
> From: Sean Whitton <spwhitton@spwhitton.name>
> Cc: 53058@debbugs.gnu.org
> Date: Wed, 02 Feb 2022 17:19:04 -0700
> 
> Hello,
> 
> On Sat 08 Jan 2022 at 08:55am +02, Eli Zaretskii wrote:
> 
> > The reasons for the problem in your case is not known: NILP should
> > have worked, as did the comparison with Qnil.  Until we understand why
> > those didn't work, I don't see how we can say anything in etc/DEBUG
> > that would both be useful and important/general enough to have there.
> >
> > My best advice is to try to understand why those conditions didn't
> > work on your system.  Maybe someone here knowns, or maybe you should
> > ask on the GDB mailing list (gdb@sourceware.org).
> 
> If I understand you correctly: we don't yet know exactly what was going
> wrong on my machine when I tried to set the conditional break point, so
> we lack a concrete case in which --enable-check-lisp-object-type
> affected debugging with GDB, and we are thus not in a position to assert
> in etc/DEBUG that --enable-check-lisp-object-type has the potential to
> have an effect on debugging with gdb?

Yes.

> When you wrote that comparisons with structs are not guaranteed to work
> with gdb, you were /not/ going as far as saying that comparisons with
> structs are never expected to work (because that would imply that
> --enable-check-lisp-object-type would often lead to issues when
> debugging)?

Yes.

> If this summary is right, I think this bug should be closed.

OK, closing.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]