Bart De VOS pointed out that removing absolute paths from the libc linker scripts is plainly wrong.
It dates from dawn ages of the original crosstool code, and is not well explained. At that time, binutils might not understand the sysroot stuff, and it was necessary to remove absolute paths in that case.
/trunk/scripts/build/libc/glibc.sh | 14 2 12 0 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
1 Original patch from gentoo: gentoo/src/patchsets/gdb/6.7.1/80_all_gdb-6.5-dwarf-stack-overflow.patch
2 -= BEGIN original header =-
3 http://bugs.gentoo.org/144833
6 2006-08-22 Will Drewry <wad@google.com>
7 Tavis Ormandy <taviso@google.com>
9 * dwarf2read.c (decode_locdesc): Enforce location description stack
11 * dwarfread.c (locval): Likewise.
13 -= END original header =-
14 diff -durN gdb-6.7.1.orig/gdb/dwarf2read.c gdb-6.7.1/gdb/dwarf2read.c
15 --- gdb-6.7.1.orig/gdb/dwarf2read.c 2007-09-05 02:51:48.000000000 +0200
16 +++ gdb-6.7.1/gdb/dwarf2read.c 2008-06-17 23:27:46.000000000 +0200
18 callers will only want a very basic result and this can become a
21 - Note that stack[0] is unused except as a default error return.
22 - Note that stack overflow is not yet handled. */
23 + Note that stack[0] is unused except as a default error return. */
26 decode_locdesc (struct dwarf_block *blk, struct dwarf2_cu *cu)
32 + stack[++stacki] = 0;
36 @@ -9261,6 +9260,16 @@
37 dwarf_stack_op_name (op));
38 return (stack[stacki]);
40 + /* Enforce maximum stack depth of size-1 to avoid ++stacki writing
41 + outside of the allocated space. Also enforce minimum > 0.
42 + -- wad@google.com 14 Aug 2006 */
43 + if (stacki >= sizeof (stack) / sizeof (*stack) - 1)
44 + internal_error (__FILE__, __LINE__,
45 + _("location description stack too deep: %d"),
48 + internal_error (__FILE__, __LINE__,
49 + _("location description stack too shallow"));
51 return (stack[stacki]);