Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Hugh O'Keeffe" <hugh.okeeffe@ashling.com>
To: <gdb@sources.redhat.com>, <crossgcc-help@sources.redhat.com>
Subject: GCC/GDB ARM support for file I/O
Date: Thu, 17 Jul 2003 08:37:00 -0000	[thread overview]
Message-ID: <003201c34c3e$7de68ad0$140aa8c0@HUGH> (raw)

Does the GCC ARM compiler support file I/O to the host computer from the
target via a GDB/debugger link (aka semihosting) ?. I want to be able to
fopen/fwrite/fread/fclose from my target application to/from a file on
the host PC for test purposes. 

I know this is possible with the ARM ADS compiler tools, however, I now
have to port some code to GCC and need a similar feature.

I have managed to get fprintf(stdout...) and fprintf(stderr...) to work
i.e. when using an RDI connection between the target and GDB (RDI is
based on the Angel Debug Protocol).

I'm using GCC 3.2.1 on a Windows host with GDB. Any help is appreciated.
I suspect I may be missing some initialisation or something from my
startup code.

Thanks in advance,

Hugh O'Keeffe



                 reply	other threads:[~2003-07-17  8:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003201c34c3e$7de68ad0$140aa8c0@HUGH' \
    --to=hugh.okeeffe@ashling.com \
    --cc=crossgcc-help@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox