This is the mail archive of the archer@sourceware.org mailing list for the Archer project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Calling -enable-pretty-printing without modifying the GUI frontend


Thanks for the warning. I think that in my case it will be ok - I'm
only adding my own pretty-printers, which have a constant number of
fields. (I've seen them pretty-printed uninitialized in the GUI, and
it looks ok.)

2009/9/4 Tom Tromey <tromey@redhat.com>:
>>>>>> "Noam" == Noam Yorav-Raphael <noamraph@gmail.com> writes:
>
> Noam> My question is whether there's a way to automatically enable pretty
> Noam> printing without the frontend calling the command - for example, it
> Noam> would be nice if I could add it to the gdbinit file. I have to work
> Noam> with a not very new version of kdevelop as a gdb frontend, and
> Noam> recompiling it is not an option. I would prefer not to use a special
> Noam> branch of gdb which has pretty printers enabled by default.
>
> Noam> Is it possible?
>
> The reason we added an explicit command is that older clients may not
> function properly with pretty-printing.
>
> For example, if you try to pretty-print an uninitialized object, you
> might get a very large number of children, causing your debug session to
> lock up or crash.
>
> So, even if it is possible, I would recommend against it.
>
> Tom
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]