summaryrefslogtreecommitdiff
path: root/toolchain/gdb
diff options
context:
space:
mode:
authorBernhard Reutner-Fischer <rep.dot.nop@gmail.com>2006-08-24 19:46:55 +0000
committerBernhard Reutner-Fischer <rep.dot.nop@gmail.com>2006-08-24 19:46:55 +0000
commitc59db40f69c9ac58293f62f7f28db995f07da962 (patch)
treed0550adcf51fa3cd35a2521086cf630b036ce462 /toolchain/gdb
parent6e6e04c3e5d331e944463e9fa8b107bfa948f49e (diff)
- remove patch that was already applied upstream
Diffstat (limited to 'toolchain/gdb')
-rw-r--r--toolchain/gdb/snapshot/770-debian_vfork-done-spelling.patch12
1 files changed, 0 insertions, 12 deletions
diff --git a/toolchain/gdb/snapshot/770-debian_vfork-done-spelling.patch b/toolchain/gdb/snapshot/770-debian_vfork-done-spelling.patch
deleted file mode 100644
index d700f768c..000000000
--- a/toolchain/gdb/snapshot/770-debian_vfork-done-spelling.patch
+++ /dev/null
@@ -1,12 +0,0 @@
-diff -ur gdb-6.3.50.20050915/gdb/linux-nat.c gdb-6.3.50.20050915-patched/gdb/linux-nat.c
---- gdb-6.3.50.20050915/gdb/linux-nat.c 2005-09-10 13:11:02.000000000 -0500
-+++ gdb-6.3.50.20050915-patched/gdb/linux-nat.c 2005-09-15 19:57:23.000000000 -0500
-@@ -458,7 +458,7 @@
- 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