Get rid of eclipse fiels once and for all.
Homogenise the references to crosstool-NG:
- the project is named "crosstool-NG"
- the front-end is named "ct-ng"
- don't use shortcuts (such as "ct-ng" to stand for "crosstool-NG")
Default action is to print help.
Don't speak of make rules when dumping help, just speak of actions.
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
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
13 #endif /* PTRACE_EVENT_FORK */
14 @@ -362,7 +362,7 @@ child_follow_fork (int follow_child)
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);
23 @@ -434,7 +434,7 @@ child_follow_fork (int follow_child)
24 generally not encounter vfork (vfork is defined to fork
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