This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Redboot GDB stubs for non-ecos application


I'm working on getting GDB stubs working for a non-ecos application, and
trying to figure out how to make this work.

It looks as if the applicaiton needs to enable interrupts, at least for
the serial port, so that control-c work.  Possibly for Ethernet for same
reason, but I'll deal with that later.

Does Redboot put breakpoint instructions at the vectors, so the
application can load it's own vectors, or does the application need to use
the same VSR table that redboot/ecos use?

If Redboot puts the break instructions on the vectors, when the
application exits, does redboot rewrite those vectors, or I guess it
doesn't really need them since it's running with interrupts off?

If someone has an example of how another Architecture does this and I
could look at that.

Thanks,

-John



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]