From: Surya Kiran Gullapalli <suryakiran.gullapalli@gmail.com>
To: gdb@sourceware.org
Subject: Re: gdb.lookup_type problem with boost::multi_index::multi_index_container
Date: Tue, 29 Jan 2013 11:58:00 -0000 [thread overview]
Message-ID: <CAKkRBO3EuSbo0jX8Z0fX2ndFB8FYCNebJUfvHM1H8iJmH0dj5Q@mail.gmail.com> (raw)
In-Reply-To: <CAKkRBO3MW5EKmG-6HDTDY1Q1-3-chNhjWnv5NDSGTg-wywTj_g@mail.gmail.com>
Is there any other way to get the required type ?
Surya
On Thu, Jan 24, 2013 at 7:23 AM, Surya Kiran Gullapalli
<suryakiran.gullapalli@gmail.com> wrote:
> Hi,
> I'm using gdb-7.5, on RHEL 6, compiled with gcc-4.7.2. I'm trying to
> write a pretty printer for boost::multi_index and ran into problems
> with gdb.lookup_type.
>
> Attached code has the following declaration.
>
> TestSet ts;
>
> Now, at the gdb command prompt, I'm performing the following
> operations (in python)
>
> gdb >> python
>> set_value = gdb.parse_and_eval('ts')
>> set_type = set_value.type.strip_typedefs()
>> t1 = set_type.template_argument(0) # Test
>> t2 = set_type.template_argument(1) # boost::mult_index::indexed_by ....
>> t3 = set_type.template_argument(2) # std::allocator<Test>
>> node_type = gdb.lookup_type('boost::multi_index::detail::multi_index_node_type < %s, %s, %s >::type' % (t1, t2, t3))
>> base = gdb.lookup_type ('boost::multi_index::detail::multi_index_base_type < %s, %s, %s >::type' % (t1, t2, t3))
>> allocator = gdb.lookup_type('boost::detail::allocator::rebind_to<%s, %s>::type' % (t3, node_type))
>> end
>
> I'm getting the node_type correctly. But gdb is unable to get types
> for 'base' and 'allocator'.
>
> ------------------------ The error for 'base' --------------------
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> gdb.error: No type named boost::detail::multi_index_base_type < Test,
> boost::multi_index::indexed_by<boost::multi_index::ordered_unique<boost::multi_index::member<Test,
> std::basic_string<char, std::char_traits<char>, std::allocator<char>
>>, &Test::s>, mpl_::na, mpl_::na>
> , boost::multi_index::ordered_unique<boost::multi_index::tag<int,
> mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na,
> mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na,
> mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::multi_i
> ndex::member<Test, int, &Test::i>, mpl_::na>,
> boost::multi_index::ordered_unique<boost::multi_index::member<Test,
> float, &Test::f>, mpl_::na, mpl_::na>, mpl_::na, mpl_::na, mpl_::na,
> mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na,
> mpl_::na, mpl_::na
> , mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>,
> std::allocator<Test> >::type.
> Error while executing Python code.
> --------------------------------------------------------------
>
> and a similar error for 'allocator'.
> as boost::multi_index_container is derived from
> boost::detail::multi_index_base_type, I'm expecting gdb to return a
> valid type for the same.
>
> Am I missing something here. ?
>
> Thanks,
> Surya
prev parent reply other threads:[~2013-01-29 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 1:54 Surya Kiran Gullapalli
2013-01-29 11:58 ` Surya Kiran Gullapalli [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=CAKkRBO3EuSbo0jX8Z0fX2ndFB8FYCNebJUfvHM1H8iJmH0dj5Q@mail.gmail.com \
--to=suryakiran.gullapalli@gmail.com \
--cc=gdb@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).