yann@96: Index: gdb-6.3/gdb/linux-nat.c
yann@96: ===================================================================
yann@96: --- gdb-6.3.orig/gdb/linux-nat.c	2004-11-14 00:36:41.000000000 -0500
yann@96: +++ gdb-6.3/gdb/linux-nat.c	2004-11-15 11:51:43.954161476 -0500
yann@96: @@ -69,7 +69,7 @@
yann@96:  #define PTRACE_EVENT_VFORK	2
yann@96:  #define PTRACE_EVENT_CLONE	3
yann@96:  #define PTRACE_EVENT_EXEC	4
yann@96: -#define PTRACE_EVENT_VFORKDONE	5
yann@96: +#define PTRACE_EVENT_VFORK_DONE	5
yann@96:  #define PTRACE_EVENT_EXIT	6
yann@96:  
yann@96:  #endif /* PTRACE_EVENT_FORK */
yann@96: @@ -362,7 +362,7 @@ child_follow_fork (int follow_child)
yann@96:  
yann@96:  	      ptrace (PTRACE_CONT, parent_pid, 0, 0);
yann@96:  	      waitpid (parent_pid, &status, __WALL);
yann@96: -	      if ((status >> 16) != PTRACE_EVENT_VFORKDONE)
yann@96: +	      if ((status >> 16) != PTRACE_EVENT_VFORK_DONE)
yann@96:  		warning ("Unexpected waitpid result %06x when waiting for "
yann@96:  			 "vfork-done", status);
yann@96:  	    }
yann@96: @@ -434,7 +434,7 @@ child_follow_fork (int follow_child)
yann@96:  	 generally not encounter vfork (vfork is defined to fork
yann@96:  	 in libpthread.so).
yann@96:  
yann@96: -	 The holding part is very easy if we have VFORKDONE events;
yann@96: +	 The holding part is very easy if we have VFORK_DONE events;
yann@96:  	 but keeping track of both processes is beyond GDB at the
yann@96:  	 moment.  So we don't expose the parent to the rest of GDB.
yann@96:  	 Instead we quietly hold onto it until such time as we can