|
From: <sv...@va...> - 2005-05-16 19:33:43
|
Author: sewardj
Date: 2005-05-16 12:47:17 +0100 (Mon, 16 May 2005)
New Revision: 3737
Modified:
trunk/coregrind/m_stacktrace.c
Log:
Fix comment.
Modified: trunk/coregrind/m_stacktrace.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/coregrind/m_stacktrace.c 2005-05-16 07:31:57 UTC (rev 3736)
+++ trunk/coregrind/m_stacktrace.c 2005-05-16 11:47:17 UTC (rev 3737)
@@ -120,7 +120,7 @@
we can safely try the old-fashioned method. */
/* This bit is supposed to deal with frames resulting from
functions which begin "pushl% ebp ; movl %esp, %ebp" (x86)
- or "pushl% ebp ; movl %esp, %ebp" (amd64). Unfortunately,
+ or "pushq %rbp ; movq %rsp, %rbp" (amd64). Unfortunately,
since we can't (easily) look at the insns at the start of
the fn, like GDB does, there's no reliable way to tell.
Hence the hack of first trying out CFI, and if that fails,
|