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

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

[debbugs-tracker] bug#15574: closed (24.3.50; Can't debug, VALMASK undef


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#15574: closed (24.3.50; Can't debug, VALMASK undefined)
Date: Thu, 17 Oct 2013 06:34:02 +0000

Your message dated Wed, 16 Oct 2013 23:33:21 -0700
with message-id <address@hidden>
and subject line Re: 24.3.50; Can't debug, VALMASK undefined
has caused the debbugs.gnu.org bug report #15574,
regarding 24.3.50; Can't debug, VALMASK undefined
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
15574: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15574
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.3.50; Can't debug, VALMASK undefined Date: Wed, 9 Oct 2013 18:56:57 +0200
Hello.

When starting gdb, I get:

warning: Got an error handling event: "No symbol "VALMASK" in current context.".

Needles to say, any debugging of Lisp objects and Lisp backtrace doesn't work.
It seems clang optimizes away VALMASK even at zero optimizing level.

Can we rearrange this somehow?  External and defined in a C-file?  Or fix 
.gdbinit to not use VALMASK?

        Jan D.



In GNU Emacs 24.3.50.1 (x86_64-apple-darwin12.5.0, NS apple-appkit-1187.39)
of 2013-10-02 on zeplin
Bzr revision: 114501 address@hidden
Windowing system distributor `Apple', version 10.3.1187
Configured using:
`configure --verbose --with-ns CFLAGS=-g3'

        Jan D.




--- End Message ---
--- Begin Message --- Subject: Re: 24.3.50; Can't debug, VALMASK undefined Date: Wed, 16 Oct 2013 23:33:21 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
Thanks for checking; marking this as done.


--- End Message ---

reply via email to

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