add fflush to file logging about memprocfs HOT 4 CLOSED

Use f:4 to log with verbose level to the file. There was an error in the guide previously which I've now resolved.

The file is not regularly flushed though so results may not be instantly visible. I should probably change that or at least add a force flush option, but it may also slow down execution significantly at the higher log levels so an option to flush after each log may be good.

If using the API on-screen console logging isn't enabled by default. You'd either have to enable it with the old way, i.e. command line options -printf and -v.

But since you're using the newer loglevel option it would be: f:4,4 if wishing to log at verbose level to both file and on-screen.

Let me know if it works better.

from memprocfs.

it works,but only when the handle of hVmm close,it will flush,i recommend add a flush interval.

from memprocfs.

I'll add a flush, possibly via some extra config option. I'm currently away over holidays though so it will have to wait until I get back home since my code signing certificate is on another computer.

from memprocfs.

I added this some time ago, but I forgot to update the documentation and also mention it here.

Nevertheless, there should now be a fflush option to the -loglevel option. See the documentation (click details): https://github.com/ufrisk/MemProcFS-dev/wiki/_CommandLine#-loglevel

It will do a fflush after each written log line if specified.

In your above example it should be like this now:

LPSTR args[] = { (LPSTR)"-device", (LPSTR)"fpga",(LPSTR)"-loglevel",(LPSTR)"fflush,f::4",(LPSTR)"-logfile",(LPSTR)"memprocfslog.txt"};
    hVmm = VMMDLL_Initialize(6, args);

I'm closing this issue since it should now be resolved. But if there should be any lingering issues or not work as intended please let me know and feel free to re-open the issue.

from memprocfs.