Re: [ECOS] EPI's ICE + gcc

["Xavier Wang" <xavierwang at ms19 dot url dot com dot tw>]

>Xavier Wang wrote:
>> The debugger's manual said that it supports both ELF and COFF formats.
But
>> when I tried to load the program, the debugger complained that the ELF
file
>> does
>> not contain .mdebug, .debug or .stab section. There are indeed many
.debug*
>> sections in the file but no one is exactly .debug, and the .mdebug is
>> explicitly
>> discarded by the link script (target.ld). I removed the discard command
to
>> add
>> back the .mdebug section and then the debugger could load the program,
but I
>> could only see the source/symbols of vectors.S
>> (in eCos\packages\hal\mips\arch\v1_3_1\src), all other parts of the
program
>> were
>> in disassembly form only. It's very strange.
>>
>> I'd searched the archives database of this mailing list and tried some
other
>> options
>> found there, such as -gdwarf-2, -gcoff, -gstabs, etc. but still failed.
Did
>> I miss
>> something?
>
>It looks like the EPI debugger only supports the stabs debugging format. If
>-gstabs isn't working for you, then you'll have to dig deeper. Perhaps on
>the GDB list ( http://sources.redhat.com/gdb )
>
>Jifl

Thanks, Jifl.

I've asked EPI about this problem. The support man said the debugger now can
handle DWARF1 (.debug, .line), Mdebug (.mdebug) and Stabs (.stab, .stabstr),
but DWARF2 is not supported. So if I can produce an executable that has one
of these supported format, the debugger will like to accept it.

The default debug option (-g) of mips-tx39-elf-gcc seems to produce DWARF2
format, and doesn't support -gdwarf or -gdwarf-1 option. So how should I
config
the link script and the compiler options to produce an executable with
either
Mdebug or Stabs debug format in it?

Thanks a lot.

-- Xavier