patches/gdb/6.4/400-mips-coredump.patch-2.4.23-29
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Dec 29 21:16:51 2009 +0100 (2009-12-29)
branch1.5
changeset 1707 b522b439a1e4
permissions -rw-r--r--
config: fix generated config files when GREP_OPTIONS set --color=always

grep is used when generating some .in files (in config.gen). If GREP_OPTIONS
contains --color=always, then the generated files will contains some escape
sequences setting the color, and mconf would choke on those escape sequences.

Always set and export an empty GREP_OPTIONS to avoid that.

Issue reported by Kevin Kirkup <kevin dot kirkup at gmail dot com> :
http://sourceware.org/ml/crossgcc/2009-12/msg00026.html
(transplanted from a5020a1facffc046d23d39a71a1b8089ca84beac)
     1 Sometime around 2.4.22-23, the mips pt_regs.h fields were reordered, breaking
     2 coredump handling by gdb for current kernels.  Update the hardcoded constants
     3 to reflect the change.
     4 --- gdb-6.2.1/gdb/mips-linux-tdep.c-orig	2004-10-29 14:23:55.000000000 -0500
     5 +++ gdb-6.2.1/gdb/mips-linux-tdep.c	2004-10-29 14:26:44.000000000 -0500
     6 @@ -53,12 +53,22 @@
     7  
     8  #define EF_REG0			6
     9  #define EF_REG31		37
    10 +
    11 +#if 0
    12  #define EF_LO			38
    13  #define EF_HI			39
    14  #define EF_CP0_EPC		40
    15  #define EF_CP0_BADVADDR		41
    16  #define EF_CP0_STATUS		42
    17  #define EF_CP0_CAUSE		43
    18 +#else
    19 +#define EF_CP0_STATUS		38
    20 +#define EF_LO			39
    21 +#define EF_HI			40
    22 +#define EF_CP0_BADVADDR		41
    23 +#define EF_CP0_CAUSE		42
    24 +#define EF_CP0_EPC		43
    25 +#endif
    26  
    27  #define EF_SIZE			180
    28