patches/gdb/6.3/770-debian_vfork-done-spelling.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu May 17 16:22:51 2007 +0000 (2007-05-17)
changeset 96 aa1a9fbd6eb8
permissions -rw-r--r--
Debug facilities:
- add a framework to easily add new ones
- add gdb as a first debug facility
- add patches for gdb
After the kernel checked its installed headers, clean up the mess of .checked.* files.
Reorder scripts/crosstool.sh:
- dump the configuration early
- renice early
- get info about build system early, when setting up the environment
- when in cross or native, the host tools are those of the build system, and only in this case
- elapsed time calculations moved to scripts/functions
Remove handling of the color: it's gone once and for all.
Update tools/addToolVersion.sh:
- handle debug facilities
- commonalise some code
- remove dead tools (cygwin, tcc)
Point to my address for bug reports.
     1 Index: gdb-6.3/gdb/linux-nat.c
     2 ===================================================================
     3 --- gdb-6.3.orig/gdb/linux-nat.c	2004-11-14 00:36:41.000000000 -0500
     4 +++ gdb-6.3/gdb/linux-nat.c	2004-11-15 11:51:43.954161476 -0500
     5 @@ -69,7 +69,7 @@
     6  #define PTRACE_EVENT_VFORK	2
     7  #define PTRACE_EVENT_CLONE	3
     8  #define PTRACE_EVENT_EXEC	4
     9 -#define PTRACE_EVENT_VFORKDONE	5
    10 +#define PTRACE_EVENT_VFORK_DONE	5
    11  #define PTRACE_EVENT_EXIT	6
    12  
    13  #endif /* PTRACE_EVENT_FORK */
    14 @@ -362,7 +362,7 @@ child_follow_fork (int follow_child)
    15  
    16  	      ptrace (PTRACE_CONT, parent_pid, 0, 0);
    17  	      waitpid (parent_pid, &status, __WALL);
    18 -	      if ((status >> 16) != PTRACE_EVENT_VFORKDONE)
    19 +	      if ((status >> 16) != PTRACE_EVENT_VFORK_DONE)
    20  		warning ("Unexpected waitpid result %06x when waiting for "
    21  			 "vfork-done", status);
    22  	    }
    23 @@ -434,7 +434,7 @@ child_follow_fork (int follow_child)
    24  	 generally not encounter vfork (vfork is defined to fork
    25  	 in libpthread.so).
    26  
    27 -	 The holding part is very easy if we have VFORKDONE events;
    28 +	 The holding part is very easy if we have VFORK_DONE events;
    29  	 but keeping track of both processes is beyond GDB at the
    30  	 moment.  So we don't expose the parent to the rest of GDB.
    31  	 Instead we quietly hold onto it until such time as we can