From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 12036@debbugs.gnu.org
Subject: bug#12036: 24.1.50; xvectype and xpr broken by change in PVEC_TYPE_MASK when macro information not available
Date: Thu, 26 Jul 2012 23:10:19 +0300 [thread overview]
Message-ID: <83ipdajnbo.fsf@gnu.org> (raw)
In-Reply-To: <50119070.8090101@cs.ucla.edu>
> Date: Thu, 26 Jul 2012 11:46:08 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: 12036@debbugs.gnu.org
>
> > (gdb) xtype
> > Lisp_Vectorlike
> > No enum type named pvec_type.
>
> I expect that I don't have this problem because the bug has been fixed
> in my tools (GCC 4.7.1 + GDB 7.4.1). I tried to work around the problem
> by putting this line into lisp.h:
>
> PUBLISH_TO_GDB ((enum pvec_type) 0); /* This also publishes PVEC_*. */
>
> but I can't easily test this, since my tools don't have the problem.
> Could you please try it? And if it doesn't work, could you
> please try adding lines like this:
>
> PUBLISH_TO_GDB (PVEC_TYPE_MASK);
>
> for values like PVEC_TYPE_MASK that do not otherwise work for you?
Unfortunately, with my ancient version of GCC, I don't even get past
CHECK_LISP_OBJECT_TYPE in xgetptr:
.gdbinit:1197: Error in sourced command file:
No symbol "CHECK_LISP_OBJECT_TYPE" in current context.
Looks like PUBLISH_TO_GDB is not doing the trick here.
Anyway, with tricky macros such as PUBLISH_TO_GDB, I'd think that
going back to using variables whose type is the enum would be better,
don't you think? We could modify PUBLISH_TO_GDB to do that.
next prev parent reply other threads:[~2012-07-26 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 18:13 bug#12036: 24.1.50; xvectype and xpr broken by change in PVEC_TYPE_MASK when macro information not available Eli Zaretskii
2012-07-26 9:14 ` Paul Eggert
2012-07-26 16:56 ` Eli Zaretskii
2012-07-26 18:03 ` Eli Zaretskii
2012-07-26 18:46 ` Paul Eggert
2012-07-26 20:10 ` Eli Zaretskii [this message]
2012-07-27 6:22 ` Paul Eggert
2012-07-27 9:40 ` Eli Zaretskii
2012-07-27 20:51 ` Paul Eggert
2012-07-28 7:30 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ipdajnbo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12036@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.