• State Accepted Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 119 subscribers
  • Views 5746 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RVDS: file access with Real View Debugger 4.0?

ssibseya

I am using the 'Arm Workbench IDE 4.0'. And I can compile the file access functions

like Following. But when run the image using the 'RealView Debugger v4.0', I can't

find out the xxx.txt file withing the system and ARM tool's directory.

FILE        *pFile=NULL;

pFile = fopen(50, (char*)"c:\\temp\\xxx.txt", "wt");    // 50 is file identifier

rv=ferror(pFile);

rv=fprintf(pFile, "test\n");

if(pFile){

        fclose(pFile);

        pFile = NULL;}

I could have used the 'printf' with debugger tool's stdio so I think that there may be method for file management.

Can I use the file management functions?

And if so how?

Parents
  • 0 Arm Employee Badge in reply to ssibseya

    Does your build give any warnings?  Does your actual code have #include <stdio.h>?

    If you rebuild after removing the '50,' and changing "wt" to "w" and are running under the debugger on a Windows host and C:\temp exists, then I expect your image to create C:\temp\xxx.txt on the host.

Reply
  • 0 Arm Employee Badge in reply to ssibseya

    Does your build give any warnings?  Does your actual code have #include <stdio.h>?

    If you rebuild after removing the '50,' and changing "wt" to "w" and are running under the debugger on a Windows host and C:\temp exists, then I expect your image to create C:\temp\xxx.txt on the host.

Children