public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug macros/9748] New: macros containing __extension__ won't run Date: Thu, 15 Jan 2009 21:06:00 -0000 [thread overview] Message-ID: <20090115210626.9748.rearnsha@gcc.gnu.org> (raw) Consider a macro, such as the following (from GCC): #define TREE_CHECK(T, CODE) __extension__ ({ __typeof (T) const __t = (T); if (TREE_CODE (__t) != (CODE)) tree_check_failed (__t, __FILE__, __LINE__, __FUNCTION__, (CODE), 0); __t; }) if the object containing the macro is compiled with -g3, then the definition is available to GDB, but this doesn't help much... (gdb) p TREE_CHECK (fntype, CALL_EXPR) No symbol "__extension__" in current context. -- Summary: macros containing __extension__ won't run Product: gdb Version: 6.7 Status: UNCONFIRMED Severity: normal Priority: P2 Component: macros AssignedTo: unassigned at sourceware dot org ReportedBy: rearnsha at gcc dot gnu dot org CC: gdb-prs at sourceware dot org http://sourceware.org/bugzilla/show_bug.cgi?id=9748 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2009-01-15 21:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-15 21:06 rearnsha at gcc dot gnu dot org [this message] 2009-01-15 21:30 ` [Bug macros/9748] " pedro at codesourcery dot com 2009-01-15 21:40 ` drow at false dot org 2009-01-15 23:39 ` pedro at codesourcery dot com 2009-01-16 0:05 ` tromey at redhat dot com
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=20090115210626.9748.rearnsha@gcc.gnu.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).