1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/patches/gdb/6.3/770-debian_vfork-done-spelling.patch Fri May 25 19:30:42 2007 +0000
1.3 @@ -0,0 +1,31 @@
1.4 +Index: gdb-6.3/gdb/linux-nat.c
1.5 +===================================================================
1.6 +--- gdb-6.3.orig/gdb/linux-nat.c 2004-11-14 00:36:41.000000000 -0500
1.7 ++++ gdb-6.3/gdb/linux-nat.c 2004-11-15 11:51:43.954161476 -0500
1.8 +@@ -69,7 +69,7 @@
1.9 + #define PTRACE_EVENT_VFORK 2
1.10 + #define PTRACE_EVENT_CLONE 3
1.11 + #define PTRACE_EVENT_EXEC 4
1.12 +-#define PTRACE_EVENT_VFORKDONE 5
1.13 ++#define PTRACE_EVENT_VFORK_DONE 5
1.14 + #define PTRACE_EVENT_EXIT 6
1.15 +
1.16 + #endif /* PTRACE_EVENT_FORK */
1.17 +@@ -362,7 +362,7 @@ child_follow_fork (int follow_child)
1.18 +
1.19 + ptrace (PTRACE_CONT, parent_pid, 0, 0);
1.20 + waitpid (parent_pid, &status, __WALL);
1.21 +- if ((status >> 16) != PTRACE_EVENT_VFORKDONE)
1.22 ++ if ((status >> 16) != PTRACE_EVENT_VFORK_DONE)
1.23 + warning ("Unexpected waitpid result %06x when waiting for "
1.24 + "vfork-done", status);
1.25 + }
1.26 +@@ -434,7 +434,7 @@ child_follow_fork (int follow_child)
1.27 + generally not encounter vfork (vfork is defined to fork
1.28 + in libpthread.so).
1.29 +
1.30 +- The holding part is very easy if we have VFORKDONE events;
1.31 ++ The holding part is very easy if we have VFORK_DONE events;
1.32 + but keeping track of both processes is beyond GDB at the
1.33 + moment. So we don't expose the parent to the rest of GDB.
1.34 + Instead we quietly hold onto it until such time as we can