Support of Pretty print

Mario Chacon

25 Jun 2009 25 Jun '09

5:51 p.m.

Hello: Is is possible that boost have gdb pretty prints??.. It's works great with std objects, it will be awesome if boost have it too!! Salu2... masch...

Attachments:

attachment.html (text/html — 181 bytes)

Show replies by date

Steven Watanabe

25 Jun 25 Jun

7:40 p.m.

AMDG Mario Chacon wrote:

...

Is is possible that boost have gdb pretty prints??..

Not that I know of. There are some for visual studio https://svn.boost.org/trac/boost/wiki/DebuggerVisualizers

...

It's works great with std objects, it will be awesome if boost have it too!!

It seems like a useful feature. Would you be willing to write some? In Christ, Steven Watanabe

Mario Chacon

26 Jun 26 Jun

2:49 p.m.

eheh... I do not know enough to write pretty prints, it's will be help if there are some example that other can continue, Do you know if exist some pretty print boost exampless? Salu2.. masch... On Thu, Jun 25, 2009 at 4:40 PM, Steven Watanabe wrote:

...

AMDG

Mario Chacon wrote:

...
Is is possible that boost have gdb pretty prints??..

Not that I know of. There are some for visual studio https://svn.boost.org/trac/boost/wiki/DebuggerVisualizers

It's works great with std objects, it will be awesome if boost have it

...
too!!

It seems like a useful feature. Would you be willing to write some?

In Christ, Steven Watanabe

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

Zachary Turner

3 p.m.

On Fri, Jun 26, 2009 at 9:49 AM, Mario Chacon wrote:

...

eheh... I do not know enough to write pretty prints, it's will be help if there are some example that other can continue, Do you know if exist some pretty print boost exampless?

It's nothing specific to boost, you just have to learn the GDB macro language. One of the difficulties in writing GDB pretty prints is that, unlike with Visual Studio debug visualizers, GDB pretty printing does not happen "automatically". You have to write a special command for every single type you want to pretty print. "printboostvariant", "printboostany", "printboostfspath", etc. It's a little bit annoying for sure. You can get around this even by writing a GDB plugin. To learn the GDB macro syntax just google for "gdb macro syntax". Additionally, you can refer to this page: http://www.yolinux.com/TUTORIALS/GDB-Commands.html#STLDEREF which, specifically contains this .gdbinit file (which is where you add macros) http://www.yolinux.com/TUTORIALS/src/dbinit_stl_views-1.03.txt that contains many examples of pretty printing STL containers. If you want to write a GDB plugin, there is not as much available info, but you can refer to this page: http://sourceware.org/ml/gdb-patches/2008-05/msg00671.html in which someone submitted a plugin for GDB to automatically display correctly STL types just by using the normal "print" statement.

Vladimir Prus

3:42 p.m.

Zachary Turner wrote:

...

On Fri, Jun 26, 2009 at 9:49 AM, Mario Chacon wrote:

...
eheh... I do not know enough to write pretty prints, it's will be help if there are some example that other can continue, Do you know if exist some pretty print boost exampless?

It's nothing specific to boost, you just have to learn the GDB macro language. One of the difficulties in writing GDB pretty prints is that, unlike with Visual Studio debug visualizers, GDB pretty printing does not happen "automatically". You have to write a special command for every single type you want to pretty print. "printboostvariant", "printboostany", "printboostfspath", etc. It's a little bit annoying for sure. You can get around this even by writing a GDB plugin.

I guess much of confusion has resulted from the fact that Mario did not say what exactly he is talking about. The GDB pretty-printers he mention have nothing to do with that inadequate-for-anything GDB macro language. These are Python pretty-printers. See: http://tromey.com/blog/?p=524 These are also documented in the development version of the GDB.

...

If you want to write a GDB plugin, there is not as much available info, but you can refer to this page:

http://sourceware.org/ml/gdb-patches/2008-05/msg00671.html

in which someone submitted a plugin for GDB to automatically display correctly STL types just by using the normal "print" statement.

That specific patch did not went further, since Python support was already in development. - Volodya

Mario Chacon

4:25 p.m.

Sorry, yes I was referring the pretty print that Volodya said. So Is it possible to start with some libraries??? Salu2... masch... On Fri, Jun 26, 2009 at 12:42 PM, Vladimir Prus wrote:

...

Zachary Turner wrote:

...
On Fri, Jun 26, 2009 at 9:49 AM, Mario Chacon wrote:

...
eheh... I do not know enough to write pretty prints, it's will be help if there are some example that other can continue, Do you know if exist some pretty print boost exampless?

It's nothing specific to boost, you just have to learn the GDB macro language. One of the difficulties in writing GDB pretty prints is that, unlike with Visual Studio debug visualizers, GDB pretty printing does not happen "automatically". You have to write a special command for every single type you want to pretty print. "printboostvariant", "printboostany", "printboostfspath", etc. It's a little bit annoying for sure. You can get around this even by writing a GDB plugin.

I guess much of confusion has resulted from the fact that Mario did not say what exactly he is talking about. The GDB pretty-printers he mention have nothing to do with that inadequate-for-anything GDB macro language. These are Python pretty-printers. See:

http://tromey.com/blog/?p=524

These are also documented in the development version of the GDB.

...
If you want to write a GDB plugin, there is not as much available info, but you can refer to this page:

http://sourceware.org/ml/gdb-patches/2008-05/msg00671.html

in which someone submitted a plugin for GDB to automatically display correctly STL types just by using the normal "print" statement.

That specific patch did not went further, since Python support was already in development.

- Volodya

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

tom fogal

2 Jul 2 Jul

9:23 p.m.

Mario Chacon writes:

...

Sorry, yes I was referring the pretty print that Volodya said. So Is it possible to start with some libraries???

Just look at the ones in libstdc++. They look fairly obvious; you just need to know the internal names for the data structures in question. I don't think you really need a boost-specific example. -tom

...

On Fri, Jun 26, 2009 at 12:42 PM, Vladimir Prus wrote:

...
Zachary Turner wrote:

...
On Fri, Jun 26, 2009 at 9:49 AM, Mario Chacon wrote:

...
eheh... I do not know enough to write pretty prints, it's will be help if there are some example that other can continue, Do you know if exist some pretty print boost exampless?

It's nothing specific to boost, you just have to learn the GDB macro language. One of the difficulties in writing GDB pretty prints is that, unlike with Visual Studio debug visualizers, GDB pretty printing does not happen "automatically". You have to write a special command for every single type you want to pretty print. "printboostvariant", "printboostany", "printboostfspath", etc. It's a little bit annoying for sure. You can get around this even by writing a GDB plugin.

I guess much of confusion has resulted from the fact that Mario did not say what exactly he is talking about. The GDB pretty-printers he mention have nothing to do with that inadequate-for-anything GDB macro language. These are Python pretty-printers. See:

http://tromey.com/blog/?p=524

These are also documented in the development version of the GDB.

...
If you want to write a GDB plugin, there is not as much available info, but you can refer to this page:

http://sourceware.org/ml/gdb-patches/2008-05/msg00671.html

in which someone submitted a plugin for GDB to automatically display correctly STL types just by using the normal "print" statement.

That specific patch did not went further, since Python support was already in development.

- Volodya

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

--000325572b8267bfec046d42c9d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Sorry, yes I was referring the pretty print that Volodya said. So Is it = possible to start with some libraries??? Salu2... masch... 
...
On Fri, Jun 26, 2009 at 12:42 PM, Vladimir Prus= <vladimi= r@codesourcery.com</a>> wrote: 

...
Zachary Turner wrote: > On Fri, Jun 26, 2009 at 9:49 AM, Mario Chacon<the.masch@gmail.com</a>> wrote: >> eheh... I do not know enough to write pretty prints, it's will= be help if >> there are some example that other can continue, Do you know if exi= st some >> pretty print boost exampless? >> > > > It's nothing specific to boost, you just have to learn the GDB mac= ro > language. =C2=A0One of the difficulties in writing GDB pretty prints i= s > that, unlike with Visual Studio debug visualizers, GDB pretty printing= > does not happen "automatically". =C2=A0You have to write a s=

 </div>I guess much of confusion has resulted from the fact that Mario did n= ot say what exactly he is talking about. The GDB pretty-printers he mention
...
have nothing to do with that inadequate-for-anything GDB macro language.
...
These are Python pretty-printers. See: =C2=A0 =C2=A0 =C2=A0 =C2=A0http://tromey.com/blog/?p=3D524" tar= get=3D"_blank">http://tromey.com/blog/?p=3D524</a> These are also documented in the development version of the GDB. 
 > If you want to write a GDB plugin, there is not as much available > info, but you can refer to this page: > > http://sourceware.org/ml/gdb-patches/2008-05/msg00671.html"= target=3D"_blank">http://sourceware.org/ml/gdb-patches/2008-05/msg00671.ht= ml</a> > > in which someone submitted a plugin for GDB to automatically display > correctly STL types just by using the normal "print" stateme= nt. </div>That specific patch did not went further, since Python support was al= ready in development. - Volodya <div><div></div>
 _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org<= /a> http://lists.boost.org/mailman/listinfo.cgi/boost-users" target= =3D"_blank">http://lists.boost.org/mailman/listinfo.cgi/boost-users</a> </div></div></blockquote></div> 

--000325572b8267bfec046d42c9d0--

--===============0305474003== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users --===============0305474003==--

5714

Age (days ago)

5721

Last active (days ago)

List overview

Download

6 comments

5 participants

participants (5)

Mario Chacon
Steven Watanabe
tom fogal
Vladimir Prus
Zachary Turner