Hi @lippmaje!
I'm using Log4mql (MT5) in my custom indicator and with 2 last versions of MT5 I'm facing an issue to watch local variables in debug. All local variables have the value "Expression could not be evaluated". If I remove Log4mql from my code, I can watch all local variables again. The strange thing is that global variables show the values normally.
In my tests, I commented all lines with LOG_ and I have this situation after the line where I declare CLogManager LogManager(...). When I commented this line too, the debug works again.
Have you faced this situation too?
Now I'm using build 2860 of MT5.
Thanks.
Marcio
Hi @lippmaje!
I'm using Log4mql (MT5) in my custom indicator and with Build 3280 (22 April 2022).
I started to use several functions like LOG_DEBUG and LOG_INFO, and with parameter you provided in the exemple_sample file. It worked half a day but suddenly my debugger started to act weirdly:
Step over didn't work well and jumped to much further into the code and obviously generated fatal errors. Even when using step into every time it acted like this.
I didn't think this could happen with a library, but I tried what Marcio Yokoyama did, commented all what was linked with library and it started to work well again.
Did you or someone else face this behaviour ?
Maybe it is linked with the computer environment ?
Thank you for you replies.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Log4mql (MT5):
A logging library similar to Log4j but for MQL.
Author: lippmaje