public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/12937] Support optimized out / unused template methods
Date: Wed, 19 Oct 2011 17:20:00 -0000	[thread overview]
Message-ID: <bug-12937-4717-CtsJOdohRY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12937-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12937

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at redhat dot com

--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2011-10-19 17:19:59 UTC ---
We've discussed a few ways to fix this.

One way would be to have the compiler emit the out-of-line instances
to a special section, which could then be put into the .debug file.
Then, gdb could call dlopen to map this into the inferior.

Another way would be to write a GCC plugin to transform the out-of-line
instances into Python code using gdb's Python API.  This could be done,
e.g., using David Malcolm's plugin
(https://fedorahosted.org/gcc-python-plugin/)
and converting gimple to Python code.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  reply	other threads:[~2011-10-19 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 16:33 [Bug c++/12937] New: " jan.kratochvil at redhat dot com
2011-10-19 17:20 ` tromey at redhat dot com [this message]
2011-11-10 19:52 ` [Bug c++/12937] " tromey at redhat dot com
2013-02-22 16: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=bug-12937-4717-CtsJOdohRY@http.sourceware.org/bugzilla/ \
    --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: link
Be 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).