Re: [Libreoffice] Examing unicode strings in gdb (while debugging LibO)

Michael Meeks <michael.meeks -AT- novell.com>
Thu, 18 Nov 2010 20:05:21 +0000


On Thu, 2010-11-18 at 09:30 +0000, Caolán McNamara wrote:

See also scratch/writer/gdbinit-cbosdo in build.git. :)


Without checking myself, are those pu macros horrifically slow or
speedy ? I vaguely recall trying something like that before, and got
whacked by astonishingly slow output.


        With the new python / gdb stuff it could be that we could add some
hooks for printing our funky types that would actually execute quickly
and be helpful :-)

        I'll add an 'easy' hack for this tomorrow :-)

        HTH,

                Michael.

-- 
 michael.meeks@novell.com  <><, Pseudo Engineer, itinerant idiot

Context

[Libreoffice] Examing unicode strings in gdb (while debugging LibO) · Giuseppe Castagno
- Re: [Libreoffice] Examing unicode strings in gdb (while debugging LibO) · Caolán McNamara
  - Re: [Libreoffice] Examing unicode strings in gdb (while debugging LibO) · Miklos Vajna
    - Re: [Libreoffice] Examing unicode strings in gdb (while debugging LibO) · Caolán McNamara
      - Re: [Libreoffice] Examing unicode strings in gdb (while debugging LibO) · Miklos Vajna
      - Re: [Libreoffice] Examing unicode strings in gdb (while debugging LibO) · Michael Meeks

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.