IEEE 695 support for MRI tools
Mark Phillips
M.S.Phillips@nortel.co.uk
Thu May 22 04:10:00 GMT 1997
Hi there,
Has anyone managed to get ieee support working?
I'm currently using MRI C compiler, XRAY debugger and HP BDM tools.
I would like to move over to gcc (for C++ support and so I use the same
host compiler for sun/hp and target compilations).
Currently I can produce IEEE files, but if the (sort of elf, m68k-psos
binutils [*]) file contains STABS debug info, the resulting ieee file
(after an objcopy) does not even load into XRAY (Error 0ED6 unknown record
header).
Has anyone managed to feed a gcc produced object file into XRAY (IEEE)
with debug info?
Cheers
Mark
Notes
=====
The object file (with the debug info) looks like this:-
bharh59a:/view/msp_RELEASE/vobs/pon/test 63% m68k-psos-objdump --header
hi.ieee
hi.ieee: file format ieee
Sections:
Idx Name Size VMA LMA File off Algn
0 .text 0000560e 00010000 00010000 00000000 2**2
CONTENTS, ALLOC, LOAD, CODE
1 .psos 00000000 00015610 00015610 00000000 2**0
ALLOC, DATA
2 .data 00000358 00015610 00015610 00000000 2**2
CONTENTS, ALLOC, LOAD, DATA
3 .bss 0000001c 00015d68 00015d68 00000000 2**3
ALLOC, DATA
4 .debug 0000d578 00000000 00000000 00000ed6 2**0
CONTENTS, DEBUGGING
[*]
The binutils/gcc is setup to use the m68k-psos target. This results in
binutils producing elf object files BUT with leading _ chars on symbol
names. I have modified gcc to match.... Maybe this wasn't a good idea!
Mark S. Phillips ESN 742 2461
msp@nortel.co.uk Tel. +44 1279 402461
More information about the crossgcc
mailing list