This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB 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] |
> Please use @dots{} here and elsewhere, it looks better in print. Should I use that in @smallexample too? I didn't think it would make sense, but let me know. > > +By default, all argument values are always printed. But this command > > +can be useful to make a backtrace more readable, for instance, by > > +reducing the amount of information printed for each frame, particularly > > +when large objects would normally be printed. > > Don't you want to mention the Adacore case, which was the reason for > this feature? I wasn't really sure of that, because we're working on the performance aspect too. We think we've improved a little bit already. But on the other hand, it's true that the only real solution to ultimate performance is through the use of pure DWARF, which is still a ways away (and AdaCore is also still supporting targets where DWARF is not available). So your suggestion was indeed a good idea, and I followed it. 2007-11-10 Joel Brobecker <brobecker@adacore.com> * gdb.texinfo (Print Settings): Add documentation for "set/show print frame-arguments". I'm also attaching the NEWS entry, which I did forget (good catch!). 2007-11-10 Joel Brobecker <brobecker@adacore.com> * NEWS: Add entry for new set/show print frame-args command. Thanks, Eli. -- Joel
Attachment:
doc-frame-args.diff
Description: Text document
Attachment:
NEWS.diff
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |