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]

Re: About "File I/O operations via GDB"


Nick Garnett wrote:
"Vincent Leclaire" <vleclaire@awox.com> writes:

Does anyone have experience with this option ? My goal is to try to route "fopens" (and the like) executed on the target to the debugging host filesystem, presumably using GDB.

Thanks for any pointers you can provide !


These operations are there to support stand-alone applications built
using just the gcc toolchain. They cannot be used from eCos.

Yet ;-). But it would require work: creating a plugin filesystem using the fileio package that called into redboot would be the way to do it (different from normal FS's as it would dramatically affect real-time response, but that's just the price to pay). I doubt anyone's working on this, so it's up to you (Vincent) if you'd want it.


The GCC toolchain contains its own stand-alone C library, called
newlib, which ultimately executes trap or syscall instructions to
handle any IO. RedBoot contains support to handle these and pass them
back to GDB. For this to work the appropriate support needs to be
included in GDB, which is not the default for most targets.

Specifically, only ARM at present. And you have to have linked your newlib app with the appropriate redboot.specs file.


Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine


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


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