]>
Commit | Line | Data |
---|---|---|
5a03b7c3 MT |
1 | Problem occurs with python and its get_current_arch () as it selects |
2 | selected_frame and current_frame while still inferior_ptid is valid for the | |
3 | original parent. But since this place it is already attached and later | |
4 | unwinders try to access it, breaking: | |
5 | -PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the first fork | |
6 | -PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the first fork | |
7 | -PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the second fork | |
8 | -PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the second fork | |
9 | -PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: finish | |
10 | +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the first fork | |
11 | +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the first fork | |
12 | +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the second fork | |
13 | +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the second fork | |
14 | +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: finish | |
15 | ||
16 | --- ./gdb/infrun.c 2009-12-21 20:26:30.000000000 +0100 | |
17 | +++ ./gdb/infrun.c 2009-12-21 20:26:11.000000000 +0100 | |
18 | @@ -375,6 +375,9 @@ follow_fork (void) | |
19 | } | |
20 | else | |
21 | { | |
22 | + /* Possibly referenced PARENT is no longer valid. */ | |
23 | + reinit_frame_cache (); | |
24 | + | |
25 | /* This pending follow fork event is now handled, one way | |
26 | or another. The previous selected thread may be gone | |
27 | from the lists by now, but if it is still around, need |