- Step 1: Navigate to the directory where the stand-alone executable is present
- *Step 2:*Execute the stand-alone application and if it fails the error message/log can be seen on the command prompt/Terminal
View Error/Warning/Display messages from a MCR standalone
2 views (last 30 days)
Show older comments
Connor Ferguson
on 23 Oct 2015
Commented: Yanjie
on 27 Jun 2024
My lab uses a standalone matlab executable created using the MCR. Under certain circumstances, users of the program will encounter an error but the only indication of the error is a "bell" sound and the attempted action will not be performed.
Is there some sort of log or display that I can access to see what error/warning/output has occurred with the "bell" sound so that I can help to troubleshoot in the source code?
Thank you, Connor
0 Comments
Accepted Answer
Sudhanshu Bhatt
on 28 Oct 2015
Hi Connor Ferguson,
I understand that your colleagues are facing issues while executing a stand-alone executable created by MATLAB.
Can you provide more information on how are your colleagues executing the stand-alone application? Also, whether the platform is Windows/Mac/Linux?
It is possible to see the error message (if generated) when the executable is run from the Windows command prompt or Terminal in Mac/Linux.
Steps to do that are mentioned below:
If this does not resolve your issue, please create a Technical Support Request by visiting the link below:
Thanks
Sudhanshu Bhatt
2 Comments
Yanjie
on 27 Jun 2024
somehow this method is not working for me, I can launch the stand alone *.exe from the CMD. But than the CMD window turns full black , doesn't show any thing.
More Answers (0)
See Also
Categories
Find more on Get Started with MuPAD in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!