0911f37
Problem occurs with python and its get_current_arch () as it selects
0911f37
selected_frame and current_frame while still inferior_ptid is valid for the
0911f37
original parent.  But since this place it is already attached and later
0911f37
unwinders try to access it, breaking:
0911f37
  -PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the first fork
0911f37
  -PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the first fork
0911f37
  -PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the second fork
0911f37
  -PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the second fork
0911f37
  -PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: finish
0911f37
  +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the first fork
0911f37
  +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the first fork
0911f37
  +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the second fork
0911f37
  +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the second fork
0911f37
  +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: finish
0911f37
0911f37
--- ./gdb/infrun.c	2009-12-21 20:26:30.000000000 +0100
0911f37
+++ ./gdb/infrun.c	2009-12-21 20:26:11.000000000 +0100
0911f37
@@ -375,6 +375,9 @@ follow_fork (void)
0911f37
 	  }
0911f37
 	else
0911f37
 	  {
0911f37
+	    /* Possibly referenced PARENT is no longer valid.  */
0911f37
+	    reinit_frame_cache ();
0911f37
+
0911f37
 	    /* This pending follow fork event is now handled, one way
0911f37
 	       or another.  The previous selected thread may be gone
0911f37
 	       from the lists by now, but if it is still around, need