On Mon, Nov 16, 2020 at 05:42:47PM +0800, Tiezhu Yang wrote: > "to into" -> "into" > > Reported-by: Sergei Shtylyov <sergei.shtyl...@gmail.com> > Signed-off-by: Tiezhu Yang <yangtie...@loongson.cn>
Acked-by: Daniel Thompson <daniel.thomp...@linaro.org> > --- > Documentation/dev-tools/kgdb.rst | 7 +++---- > 1 file changed, 3 insertions(+), 4 deletions(-) > > diff --git a/Documentation/dev-tools/kgdb.rst > b/Documentation/dev-tools/kgdb.rst > index 77b688e..4345624 100644 > --- a/Documentation/dev-tools/kgdb.rst > +++ b/Documentation/dev-tools/kgdb.rst > @@ -63,10 +63,9 @@ will want to turn on ``CONFIG_DEBUG_INFO`` which is called > It is advised, but not required, that you turn on the > ``CONFIG_FRAME_POINTER`` kernel option which is called > :menuselection:`Compile > the kernel with frame pointers` in the config menu. This option inserts code > -to into the compiled executable which saves the frame information in > -registers or on the stack at different points which allows a debugger > -such as gdb to more accurately construct stack back traces while > -debugging the kernel. > +into the compiled executable which saves the frame information in registers > +or on the stack at different points which allows a debugger such as gdb to > +more accurately construct stack back traces while debugging the kernel. > > If the architecture that you are using supports the kernel option > ``CONFIG_STRICT_KERNEL_RWX``, you should consider turning it off. This > -- > 2.1.0 > _______________________________________________ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
