: >
: > 3. Remote debugging. Has anyone looked at having the compiler generate gdb
: > compatible symbol information? I then see creating a small process that
: > runs in the target system with gdb communicating over a serial link. I
: > seem to recall gdb having SOME support for 16-bit x86 code and support for
: > remote debugging over a serial cable.
:
: Don't know alot about this.
:
The compiler used for ELKS, bcc, uses the original a.out format from MINIX
(and essentially v6 unix) ZMAGIC header. This format supports limited
symbol information. None of the later linux tools (COFF/ELF format) use
this older format. So - the good news is that the compiler, as86
and ld86 sources are there, and the projects aren't that big. The bad news
is that I think it would take quite alot of work to get a debugger going on this,
even if were running on a linux 386 box. A quick look at bin-utils would
better answer this.
There are some pretty extreme memory limitations with all ELKS binaries as
well. The compiler doesn't support FAR data, for instance.
Greg
