public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/43912] lambda debug info does not describe captured variables Date: Wed, 28 Jul 2010 11:41:00 -0000 [thread overview] Message-ID: <20100728114107.10505.qmail@sourceware.org> (raw) In-Reply-To: <bug-43912-360@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from jakub at gcc dot gnu dot org 2010-07-28 11:41 ------- Created an attachment (id=21334) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21334&action=view) gcc46-pr43912.patch Untested proof of concept patch (which handles just non-templates though). The captured vars can be printed fine in the debugger, though no testing of more complicated captures (like arrays etc.) has been done. Not sure how to handle the template case though, so not working on this anymore. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43912
prev parent reply other threads:[~2010-07-28 11:41 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-27 19:57 [Bug c++/43912] New: " tromey at gcc dot gnu dot org 2010-07-27 15:14 ` [Bug c++/43912] " jakub at gcc dot gnu dot org 2010-07-28 11:41 ` jakub at gcc dot gnu dot org [this message]
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=20100728114107.10505.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).