native gdb+simulator

native gdb+simulator

[Daniel Drotos]

Hi,

Is it possible to include a simultor if gdb is configured for the
host's target?

I mean, for example I config and compile on elf32-i386 (e.g. linux)
and I'd like to use this bfd target to read in the file to be
debugged, but use a (own written) simulator to actually execute the
code.

Is it possible to hack feature like this into the gdb without
introducing a new bfd target?

Daniel

native gdb+simulator

[Daniel Drotos]

Hi,

Is it possible to include a simultor if gdb is configured for the
host's target?

I mean, for example I config and compile on elf32-i386 (e.g. linux)
and I'd like to use this bfd target to read in the file to be
debugged, but use a (own written) simulator to actually execute the
code.

Is it possible to hack feature like this into the gdb without
introducing a new bfd target?

Daniel

Re: native gdb+simulator

[Andrew Cagney]

Daniel Drotos wrote:
> 
> Hi,
> 
> Is it possible to include a simultor if gdb is configured for the
> host's target?

Yes.

> I mean, for example I config and compile on elf32-i386 (e.g. linux)
> and I'd like to use this bfd target to read in the file to be
> debugged, but use a (own written) simulator to actually execute the
> code.

Yes.

> Is it possible to hack feature like this into the gdb without
> introducing a new bfd target?

Yes.


If there is a simulator in the .../sim directory and GDB knows about it
(see gdb/config/*/*.mt) it will be linked in.  The file
include/remote-sim.h specifies the interface and the various sim
sub-directories contain examples.

Should I infer that there could be a GPL'd i386 simulator in the making?

	Andrew

Re: native gdb+simulator

[Daniel Drotos]

On Wed, 14 Apr 1999, Andrew Cagney wrote:

[ ... ]
Thanks for the info!

> Should I infer that there could be a GPL'd i386 simulator in the making?

No. We are working on GPL'd development environment for MCS51 based
micros. C compiler is working now, simulator is ready too. It would be
nice to use gdb as a sphisticated interface to the simulator.

My idea is that hex file generated by the compiler/linker could be
placed in an empty elf file, for example in a .mcs51code section which
could be passed to the simulator by the gdb-sim interface. If the
compiler could produce debug info in stab format then it could be
included into that empty 'template' elf file too, so gdb could debug
it, I hope.

So it doesn't matter what the native target is, any kind of elf could
be usabe I think.

Daniel