Re: GDB manual changes

[Stan Shebs <shebs at apple dot com>]

Eli Zaretskii wrote:
> 
> > ! @c below produces an acceptable overful hbox. --mew 13aug1993
> >   @cindex frameless execution
> >   Some compilers provide a way to compile functions so that they operate
> > ! without stack frames.  (For example, the @code{@value{GCC}} option
> > ! @samp{-fomit-frame-pointer} generates functions without a frame.)
> >   This is occasionally done with heavily used library functions to save
> >   the frame setup time.  @value{GDBN} has limited facilities for dealing
> >   with these function invocations.  If the innermost function invocation
> > --- 3661,3675 ----
> >   they are assigned by @value{GDBN} to give you a way of designating stack
> >   frames in @value{GDBN} commands.
> >
> > ! @c The -fomit-frame-pointer below perennially causes hbox overflow
> > ! @c underflow problems.
> >   @cindex frameless execution
> >   Some compilers provide a way to compile functions so that they operate
> > ! without stack frames.  (For example, the @value{GCC} option
> > ! @example
> > ! @samp{-fomit-frame-pointer}
> > ! @end example
> > ! generates functions without a frame.)
> 
> Ouch!  Isn't there a better way of avoiding overflow?  I usually put
> in some slack words to do that.  Do you want me to try to find a
> better solution?

Sure, if you can - I tinkered a while with no luck.  The trick is to
make it work both normally and with @smallbook.  Doing it as an example
or display guarantees it will work permanently...

> Anyway, you probably want @noindent after the @example, if this is
> left alone.

Oh yeah, good catch!

Stan