Subject: bug#15574: closed (Re: 24.3.50; Can't debug, VALMASK undefined)

From: [email-masked] (GNU bug Tracking System)
Date: Thu, 17 Oct 2013 06:34:03 +0000

Your bug report

#15574: 24.3.50; Can't debug, VALMASK undefined

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
15574: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15574
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: 24.3.50; Can't debug, VALMASK undefined
From: Paul Eggert <[email-masked]>
To: Jan Djärv <[email-masked]>
Cc: [email-masked]
Date: Wed, 16 Oct 2013 23:33:21 -0700
List-Id: <debbugs-submit.debbugs.gnu.org>

Thanks for checking; marking this as done.

Subject: 24.3.50; Can't debug, VALMASK undefined
From: Jan Djärv <[email-masked]>
To: [email-masked]
Date: Wed, 9 Oct 2013 18:56:57 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

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 [email-masked]
Windowing system distributor `Apple', version 10.3.1187
Configured using:
`configure --verbose --with-ns CFLAGS=-g3'

	Jan D.