public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/66069] New -fkeep-all-method-instances Date: Fri, 08 May 2015 13:17:00 -0000 [thread overview] Message-ID: <bug-66069-4-xFZpyLIpR6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66069-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66069 Jan Kratochvil <jan.kratochvil at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmuldoon at redhat dot com --- Comment #3 from Jan Kratochvil <jan.kratochvil at redhat dot com> --- I think so but that would require the source files available. So far 'compile print' (for C) generates all the context only from DWARF - this case was this PR's goal. The source files may not match well for *-debuginfo.rpm packaged binaries but IMO there is no chance for more complex debugging due to the -O2 -g debug info limitations.
prev parent reply other threads:[~2015-05-08 13:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-08 8:11 [Bug debug/66069] New: " jan.kratochvil at redhat dot com 2015-05-08 8:44 ` [Bug debug/66069] " jan.kratochvil at redhat dot com 2015-05-08 13:04 ` manu at gcc dot gnu.org 2015-05-08 13:17 ` jan.kratochvil at redhat dot com [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=bug-66069-4-xFZpyLIpR6@http.gcc.gnu.org/bugzilla/ \ --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).