Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chris Moller <cmoller@redhat.com>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: pr9065 patch
Date: Fri, 12 Mar 2010 14:22:00 -0000	[thread overview]
Message-ID: <4B9A4E22.8070905@redhat.com> (raw)
In-Reply-To: <m3fx46cznk.fsf@fleche.redhat.com>

On 03/11/10 16:32, Tom Tromey wrote:
>
> I guess the problem is that type_id::name is an inlined function with no
> out-of-line instance in libstdc++.  So, there is no way to call it.
>    

Yeah, I tried it anyway with a few variation of 
find_function_in_inferior ("std::type_info.name",...).  Didn't work, 
which is why I was using a fake-out approach.

>
> Chris>  +static struct value *
> Chris>  +evaluate_subexp_for_typeid_type (struct expression *exp, int *pos)
> Chris>  +     __attribute__ ((noinline));
>
> Just remove this.  For future reference, you can't use __attribute__
> unconditionally in (most of) gdb, you have to hide it behind a define.
> See defs.h.
>    

Yeah, that was just there for debugging to keep the fcn from being 
inlined--I meant to take it out before making the patch.

I'm incorporating what I can of the rest of your comments, and trying to 
figure out how to do a "not-outlined method."


  reply	other threads:[~2010-03-12 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 20:38 Chris Moller
2010-03-10  4:11 ` Eli Zaretskii
2010-03-10 12:34   ` Chris Moller
2010-03-11 21:32 ` Tom Tromey
2010-03-12 14:22   ` Chris Moller [this message]
2010-03-22 12:19   ` pr9065 patch (the typeid thing) Chris Moller

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=4B9A4E22.8070905@redhat.com \
    --to=cmoller@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /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