public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/12065] New: Configuration of backtrace display (feature)
@ 2010-09-27 13:45 midenok at bk dot ru
  0 siblings, 0 replies; only message in thread
From: midenok at bk dot ru @ 2010-09-27 13:45 UTC (permalink / raw)
  To: gdb-prs

Sometimes template arguments pollute stack trace to make it very difficult to
read. The example below is not the worst case ever. Please, enable the facility
to turn off printing of template types inside the backtrace. Even more, it would
be handy to turn off function namespaces too. And more: turning off full path
names makes even cleaner look.

Possible commands may be:

set print backtrace templates off
set print backtrace namespaces off
set print backtrace pathnames off

Example:

#4 0x005b8dd5 in
boost::interprocess::detail::private_node_pool_impl<boost::interprocess::segment_manager_base<boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0u> > >::purge_chunks (this=0xaf3bf274)
at /usr/include/boost/interprocess/allocators/detail/node_pool.hpp:246
#5 0x005b8df5 in ~private_node_pool_impl (this=0xaf3bf274) at
/usr/include/boost/interprocess/allocators/detail/node_pool.hpp:83
#6 0x005b9716 in
boost::interprocess::detail::placement_destroy<boost::interprocess::detail::shared_node_pool<boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0u>, boost::interprocess::iset_index>,
24u, 64u> >::destroy_n (this=0xbfb5b154, mem=0xaf3bf274, num=1,
destroyed=@0xbfb5b084) at
/usr/include/boost/interprocess/allocators/detail/node_pool.hpp:363
#7 0x005af428 in boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0u>,
boost::interprocess::iset_index>::priv_generic_named_destroy<char>
(this=0xaf3bf004, name=0x5c7cc0
"N5boost12interprocess6detail16shared_node_poolINS0_15segment_managerIcNS0_15rbtree_best_fitINS0_12mutex_familyENS0_10offset_ptrIvEELj0EEENS0_10iset_indexEEELj24ELj64EEE",
index=@0xaf3bf060, table=@0xbfb5b154, is_intrusive_index=
{<boost::interprocess::detail::integral_constant<bool,true>> = {static value =
<optimized out>}, static value = <optimized out>}) at
/usr/include/boost/interprocess/segment_manager.hpp:936

Example after turning off template print:

#4 0x005b8dd5 in
boost::interprocess::detail::private_node_pool_impl<...>::purge_chunks
(this=0xaf3bf274) at
/usr/include/boost/interprocess/allocators/detail/node_pool.hpp:246
#5 0x005b8df5 in ~private_node_pool_impl (this=0xaf3bf274) at
/usr/include/boost/interprocess/allocators/detail/node_pool.hpp:83
#6 0x005b9716 in boost::interprocess::detail::placement_destroy<...>::destroy_n
(this=0xbfb5b154, mem=0xaf3bf274, num=1, destroyed=@0xbfb5b084) at
/usr/include/boost/interprocess/allocators/detail/node_pool.hpp:363
#7 0x005af428 in
boost::interprocess::segment_manager<...>::priv_generic_named_destroy<...>
(this=0xaf3bf004, name=0x5c7cc0
"N5boost12interprocess6detail16shared_node_poolINS0_15segment_managerIcNS0_15rbtree_best_fitINS0_12mutex_familyENS0_10offset_ptrIvEELj0EEENS0_10iset_indexEEELj24ELj64EEE",
index=@0xaf3bf060, table=@0xbfb5b154, is_intrusive_index=
{<boost::interprocess::detail::integral_constant<bool,true>> = {static value =
<optimized out>}, static value = <optimized out>}) at
/usr/include/boost/interprocess/segment_manager.hpp:936

Example after turning off function namespaces:

#4 0x005b8dd5 in purge_chunks (this=0xaf3bf274) at
/usr/include/boost/interprocess/allocators/detail/node_pool.hpp:246
#5 0x005b8df5 in ~private_node_pool_impl (this=0xaf3bf274) at
/usr/include/boost/interprocess/allocators/detail/node_pool.hpp:83
#6 0x005b9716 in destroy_n (this=0xbfb5b154, mem=0xaf3bf274, num=1,
destroyed=@0xbfb5b084) at
/usr/include/boost/interprocess/allocators/detail/node_pool.hpp:363
#7 0x005af428 in priv_generic_named_destroy<...> (this=0xaf3bf004, name=0x5c7cc0
"N5boost12interprocess6detail16shared_node_poolINS0_15segment_managerIcNS0_15rbtree_best_fitINS0_12mutex_familyENS0_10offset_ptrIvEELj0EEENS0_10iset_indexEEELj24ELj64EEE",
index=@0xaf3bf060, table=@0xbfb5b154, is_intrusive_index=
{<integral_constant<bool,true>> = {static value = <optimized out>}, static value
= <optimized out>}) at /usr/include/boost/interprocess/segment_manager.hpp:936

Example after turning off path names:

#4 0x005b8dd5 in purge_chunks (this=0xaf3bf274) at node_pool.hpp:246
#5 0x005b8df5 in ~private_node_pool_impl (this=0xaf3bf274) at node_pool.hpp:83
#6 0x005b9716 in destroy_n (this=0xbfb5b154, mem=0xaf3bf274, num=1,
destroyed=@0xbfb5b084) at node_pool.hpp:363
#7 0x005af428 in priv_generic_named_destroy<...> (this=0xaf3bf004, name=0x5c7cc0
"N5boost12interprocess6detail16shared_node_poolINS0_15segment_managerIcNS0_15rbtree_best_fitINS0_12mutex_familyENS0_10offset_ptrIvEELj0EEENS0_10iset_indexEEELj24ELj64EEE",
index=@0xaf3bf060, table=@0xbfb5b154, is_intrusive_index=
{<integral_constant<bool,true>> = {static value = <optimized out>}, static value
= <optimized out>}) at segment_manager.hpp:936

-- 
           Summary: Configuration of backtrace display (feature)
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: midenok at bk dot ru
                CC: gdb-prs at sourceware dot org


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-09-27 13:45 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-27 13:45 [Bug c++/12065] New: Configuration of backtrace display (feature) midenok at bk dot ru

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).