Actually, it is possible. It's a bit of a mess, and can't be done directly,
but it's possible. Have gcc generate an elf file rather than a.out format.
Then use:
msp430-objdump -dST --disassembler-options=IAR prog.elf > prog_iar.s43
This generates an IAR assembly format file, which can be assembled and
linked by the IAR assembler and linker (which can be downloaded from TI, if
you don't already have it).
You don't get symbolic information about variables this way, and the whole
program looks like a single assembly file, with the C code as comments.
It's not great, but it is a lot better than no debugging! There are some
other posts in the mspgcc mailing list archives covering this in more
detail.
However, now that gdb has come so much further, it probably makes more sense
to try to find out what is going wrong there, and fix that. You'll come out
of it with a much more complete debugging system, and your experiance will
be more usefull to others as well (both gdb developers and users).
David
> nope...
>
> what's the prob with gdb?
> ~d
>
>
> On Wednesday 13 November 2002 12:19, Bernard MONDAN wrote:
> > Hello,
> >
> > I have some problems using GDB with my Win 2$$$ / Cygwin system, and I
> > must go forward with my project.
> > Is it possible to convert the a.out file to a file like file.d43 to be
> > used by the C-SPY debuger ??
> >
> > Thank You
> >
> > Bernard o(°+°)o
> >
> >
> > [email protected]
> >
