summaryrefslogtreecommitdiff
path: root/toolchain/gdb/6.3/770-debian_vfork-done-spelling.patch
diff options
context:
space:
mode:
authorEric Andersen <andersen@codepoet.org>2005-04-14 08:05:03 +0000
committerEric Andersen <andersen@codepoet.org>2005-04-14 08:05:03 +0000
commitbb000d426847ad94fc54f9e37ccb5d77b8c08ab4 (patch)
tree88de64c6f2dce029f4be1b2bd87998ab69f1312a /toolchain/gdb/6.3/770-debian_vfork-done-spelling.patch
parent1f916f68356bbd845d3daee9a52d293e1d894be5 (diff)
Add a bunch of patches snarfed from the debian gdb package
Diffstat (limited to 'toolchain/gdb/6.3/770-debian_vfork-done-spelling.patch')
-rw-r--r--toolchain/gdb/6.3/770-debian_vfork-done-spelling.patch31
1 files changed, 31 insertions, 0 deletions
diff --git a/toolchain/gdb/6.3/770-debian_vfork-done-spelling.patch b/toolchain/gdb/6.3/770-debian_vfork-done-spelling.patch
new file mode 100644
index 000000000..f65db8d09
--- /dev/null
+++ b/toolchain/gdb/6.3/770-debian_vfork-done-spelling.patch
@@ -0,0 +1,31 @@
+Index: gdb-6.3/gdb/linux-nat.c
+===================================================================
+--- gdb-6.3.orig/gdb/linux-nat.c 2004-11-14 00:36:41.000000000 -0500
++++ gdb-6.3/gdb/linux-nat.c 2004-11-15 11:51:43.954161476 -0500
+@@ -69,7 +69,7 @@
+ #define PTRACE_EVENT_VFORK 2
+ #define PTRACE_EVENT_CLONE 3
+ #define PTRACE_EVENT_EXEC 4
+-#define PTRACE_EVENT_VFORKDONE 5
++#define PTRACE_EVENT_VFORK_DONE 5
+ #define PTRACE_EVENT_EXIT 6
+
+ #endif /* PTRACE_EVENT_FORK */
+@@ -362,7 +362,7 @@ child_follow_fork (int follow_child)
+
+ ptrace (PTRACE_CONT, parent_pid, 0, 0);
+ waitpid (parent_pid, &status, __WALL);
+- if ((status >> 16) != PTRACE_EVENT_VFORKDONE)
++ if ((status >> 16) != PTRACE_EVENT_VFORK_DONE)
+ warning ("Unexpected waitpid result %06x when waiting for "
+ "vfork-done", status);
+ }
+@@ -434,7 +434,7 @@ child_follow_fork (int follow_child)
+ generally not encounter vfork (vfork is defined to fork
+ in libpthread.so).
+
+- The holding part is very easy if we have VFORKDONE events;
++ The holding part is very easy if we have VFORK_DONE events;
+ but keeping track of both processes is beyond GDB at the
+ moment. So we don't expose the parent to the rest of GDB.
+ Instead we quietly hold onto it until such time as we can