This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[commit] Initialize the sentinel frame's ID.
- From: Andrew Cagney <ac131313 at redhat dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Fri, 04 Apr 2003 09:52:03 -0500
- Subject: [commit] Initialize the sentinel frame's ID.
Hello,
This ensures that the sentinel frame's ID is initialized. It stops the
panic in mi-cli.exp.
committed,
Andrew
PS: It, for my local testing, also made the memory corruption bug
disappear again.
2003-04-04 Andrew Cagney <cagney at redhat dot com>
* frame.c (create_sentinel_frame): Initialize the sentinel frame's
ID to NULL.
Index: frame.c
===================================================================
RCS file: /cvs/src/src/gdb/frame.c,v
retrieving revision 1.93
diff -u -r1.93 frame.c
--- frame.c 1 Apr 2003 19:11:01 -0000 1.93
+++ frame.c 4 Apr 2003 14:44:24 -0000
@@ -512,6 +512,10 @@
frame's PC may require information such as the frame's thread's
stop reason. Is it possible to get to that? */
frame->pc = frame_pc_unwind (frame);
+ /* Make the sentinel frame's ID valid, but invalid. That way all
+ comparisons with it should fail. */
+ frame->id_p = 1;
+ frame->id = null_frame_id;
return frame;
}