Compiled application does not write to diary log file

20 views (last 30 days)
Hi all,
I have created a project using app designer and a number of functions. To keep track of how the calculation routes through the various functions I save comments in a log file using the diary() function and many fprintf() functions (see simplified example code below). This all works perfectly when run through matlab.
However, when I run a compiled version of the project, the log file is completely empty, even though the log file itself is created. (other files are also created/saved correctly).
I assume it's because there is no command window... for fprintf() to write to...? The same happens on my colleagues system.
Is there a way around this? Or do I need to write a dedicated logging function?
TIA, Mark.
R2019b
function mlappGUI()
main()
end
function main()
diary('c:\MatLab\logFile.log') %starts the log file
sub1()
sub2()
diary off
end
function sub1()
fprintf('subFunction1 : log file comment\n');
end
function sub2()
fprintf('subFunction2 : log file comment\n');
end
  1 Comment
Dani
Dani on 19 Jun 2020
If I compile your example (mcc -e mlappGUI.m) und run the exe then I do get the logfile with all its entries. This is with 2020a.
But I have come across this problem before. I was relying on diary for logging warnings and errors in my deployed applications (yes, lazy, but efficient, saves you adding endless try-catch statements) and with the introduction of 2019b it stopped working. The problem was that it did not stop to work entierly, so simple test cases worked for me but my full application it did not. Difficult to debug. So, I'm not sure if your test script is one of the simple cases or if in 2020a this started working properly again.

Sign in to comment.

Accepted Answer

Fangjun Jiang
Fangjun Jiang on 16 Jan 2020
I think you are right. The cause is that there is no Command Window in your compiled app.
I would suggest writing to a specific file. Use fid=fopen() to create a FID and then fprintf(fid,'log text')
You can switch to Command Window when forcing fid to be 1.
fprintf(1,'abc\n') is the same as display('abc')
  3 Comments
Fangjun Jiang
Fangjun Jiang on 17 Jan 2020
When you debug during development, force logID to be 1 somewhere then it will print to the Command Window. Run diary() outside of your app to save the log into a file.

Sign in to comment.

More Answers (0)

Categories

Find more on C Shared Library Integration in Help Center and File Exchange

Products


Release

R2019b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!