This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[PATCH/i386newframe] Indentation fix
- From: Mark Kettenis <kettenis at chello dot nl>
- To: gdb-patches at sources dot redhat dot com
- Date: Sun, 18 May 2003 19:52:24 +0200 (CEST)
- Subject: [PATCH/i386newframe] Indentation fix
Checked in.
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* i386-tdep.c (i386_frame_cache): Fix indentation of comment.
Index: i386-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/i386-tdep.c,v
retrieving revision 1.138.2.13
diff -u -p -r1.138.2.13 i386-tdep.c
--- i386-tdep.c 18 May 2003 09:44:12 -0000 1.138.2.13
+++ i386-tdep.c 18 May 2003 17:51:17 -0000
@@ -703,14 +703,14 @@ i386_frame_cache (struct frame_info *nex
cache = i386_alloc_frame_cache ();
*this_cache = cache;
-/* In principle, for normal frames, %ebp holds the frame pointer,
- which holds the base address for the current stack frame. However,
- for functions that don't need it, the frame pointer is optional.
- For these "frameless" functions the frame pointer is actually the
- frame pointer of the calling frame. Signal trampolines are just a
- special case of a "frameless" function. They (usually) share their
- frame pointer with the frame that was in progress when the signal
- occurred. */
+ /* In principle, for normal frames, %ebp holds the frame pointer,
+ which holds the base address for the current stack frame.
+ However, for functions that don't need it, the frame pointer is
+ optional. For these "frameless" functions the frame pointer is
+ actually the frame pointer of the calling frame. Signal
+ trampolines are just a special case of a "frameless" function.
+ They (usually) share their frame pointer with the frame that was
+ in progress when the signal occurred. */
frame_unwind_register (next_frame, I386_EBP_REGNUM, buf);
cache->base = extract_unsigned_integer (buf, 4);