summaryrefslogtreecommitdiff
path: root/toolchain/gdb/6.3/400-mips-coredump.patch-2.4.23-29
diff options
context:
space:
mode:
authorManuel Novoa III <mjn3@codepoet.org>2005-08-22 21:50:51 +0000
committerManuel Novoa III <mjn3@codepoet.org>2005-08-22 21:50:51 +0000
commit25db1e348fb6ab55917ca22c538bca28e4bc1b1f (patch)
tree59a9d5249ceaad4a865ed987f9d3e05600a4d9ee /toolchain/gdb/6.3/400-mips-coredump.patch-2.4.23-29
parent9b0555f23f9652e80dff68c96481e748bd74b084 (diff)
The mips kernel maintainers reverted the change. So the mips coredump patch is no longer needed for 2.4.30+.
Diffstat (limited to 'toolchain/gdb/6.3/400-mips-coredump.patch-2.4.23-29')
-rw-r--r--toolchain/gdb/6.3/400-mips-coredump.patch-2.4.23-2928
1 files changed, 28 insertions, 0 deletions
diff --git a/toolchain/gdb/6.3/400-mips-coredump.patch-2.4.23-29 b/toolchain/gdb/6.3/400-mips-coredump.patch-2.4.23-29
new file mode 100644
index 000000000..4e17ba7be
--- /dev/null
+++ b/toolchain/gdb/6.3/400-mips-coredump.patch-2.4.23-29
@@ -0,0 +1,28 @@
+Sometime around 2.4.22-23, the mips pt_regs.h fields were reordered, breaking
+coredump handling by gdb for current kernels. Update the hardcoded constants
+to reflect the change.
+--- gdb-6.2.1/gdb/mips-linux-tdep.c-orig 2004-10-29 14:23:55.000000000 -0500
++++ gdb-6.2.1/gdb/mips-linux-tdep.c 2004-10-29 14:26:44.000000000 -0500
+@@ -53,12 +53,22 @@
+
+ #define EF_REG0 6
+ #define EF_REG31 37
++
++#if 0
+ #define EF_LO 38
+ #define EF_HI 39
+ #define EF_CP0_EPC 40
+ #define EF_CP0_BADVADDR 41
+ #define EF_CP0_STATUS 42
+ #define EF_CP0_CAUSE 43
++#else
++#define EF_CP0_STATUS 38
++#define EF_LO 39
++#define EF_HI 40
++#define EF_CP0_BADVADDR 41
++#define EF_CP0_CAUSE 42
++#define EF_CP0_EPC 43
++#endif
+
+ #define EF_SIZE 180
+