Re: v850-elf-gcc produces corrupted debugging info

[Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>]

Am Sat, 06 Jun 1998 schrieb Nick Clifton:
>[snip]
>
>: and linked it with
>: 
>: v850-elf-ld -v -o gnu.out gnu.o
>: ../lib/gcc-lib/v850-elf/egcs-2.91.34/libgcc.a --entry _main -Ttext 0x0
>: --oformat elf32-v850
>: GNU ld version 2.9.4 (with BFD 980602)
>: 
>: The resulting gnu.out is corrupted. I cannot load it into our debugger and
>: v850-elf-objdump -d --source segfaults on it.
>: 
>: Thanks,
>: Franz.
>
>Well the problem appears to be the '-Ttext 0x0' switch to the linker.
>If you omit this, then everything works fine.  Since the v850 reserves
>addresses around 0 for the .zdata section, this going to cause some
>problems.  (Of course ld ought to detect this conflict and report it -
>this is something I will look into).  Anyway if you must put the .text
>section at 0 then I suggest you create your own linker script to do it
>for you.

Aah! Thanks for the info! It works with -T 0x1000. I know nearly nothing about
the v850, a colleague asked me (seems I'm becoming the gcc-specialist in our
company ;-) for a cross-compiler for it so he could compile our ROM-monitor and
a demo program for HLL debugging.

BTW, should the v850 support -gdwarf-2? The compiler rejects -gdwarf-1 and
accepts -gdwarf-2, but then produces code not acceptable for the
assembler (same testcode).

Thanks,
Franz.