From bbb5013f2120672fa5b5d73abb33f889a90896e6 Mon Sep 17 00:00:00 2001 From: John Gilmore Date: Sun, 20 Jan 1991 03:59:13 +0000 Subject: [PATCH] Allow gdb functions to specify where a line should wrap if it exceeds the size of a terminal line. Use it to make the output prettier. --- gdb/doc/gdbint.texinfo | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index eb084e734f..a7bc0956c2 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -2,7 +2,7 @@ GDB Internals documentation This needs to be wrapped in texinfo stuff... -Cleanups + Cleanups Cleanups are a structured way to deal with things that need to be done later. When your code does something (like malloc some memory, or open @@ -45,6 +45,27 @@ since they might never return to your code (they "longjmp" instead). + Wrapping output lines + +Output that goes through printf_filtered or fputs_filtered or +fputs_demangled needs only to have calls to wrap_here() added +in places that would be good breaking points. The utility routines +will take care of actually wrapping if the line width is exceeded. + +The argument to wrap_here() is an indentation string which is printed +ONLY if the line breaks there. This argument is saved away and used +later. It must remain valid until the next call to wrap_here() or +until a newline has been printed through the *_filtered functions. +Don't pass in a local variable and then return! + +It is usually best to call wrap_here() after printing a comma or space. +If you call it before printing a space, make sure that your indentation +properly accounts for the leading space that will print if the line wraps +there. + + + + Configuring GDB for release