Debugging the DLL? In MT4 and MT5 - page 15
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
At the moment there is one point in the rules for which a ban is declared, so the number of the point does not need to be clarified. But this point is vague and lists several possible reasons:
6. Repeated violation of the rules, ignoring the comments of the moderator, and even more - open disrespect for the Administration of an Internet resource, shall lead to the blocking of the account ("ban").
Question: what exactly was the reason in this case (I'm not asking in defense of the banned, but I'm asking as it is)?
About this - For repeatedly ignoring moderator's comments, openly disrespecting administration of the resource....
As for the disrespect you know, but about the remarks, so here's an example:
Academic and Prival get a warning for trolling.
The next time will be a ban for some time.
...
Hello!
Excuse me, could you explain more simply what this is all about, I'd also like to be kept up to date in case it comes in handy?
For example, what does it mean: "...possibility to debug in DLL..." or "-Give debugging to DLL..." is the same thing or different things?
Hello!
Excuse me, but could you explain more simply what this is all about, because I want to be aware of it too, in case it comes in handy?
For example, what does it mean: "...possibility to debug in DLL..." or "-Give debug to DLL..." is the same thing or different things?
I think they meant the possibility to debug MQL programs with an attached DLL using MetaEditor's built-in debugger. For security reasons the Developers don't allow this.
Then how do you understand the expression?
"We've already once conceded to traders asking "let us debug in a DLL" and immediately got an EX4 decompiler."
After all, MT4 didn't have a built-in debugger at all.
P.S. You just don't want to waste your time and then it will turn out to be closed for security reasons.
Then how do you understand the expression?
"We've already once conceded to traders asking "let us debug in a DLL" and immediately got an EX4 decompiler."
After all, MT4 didn't have a built-in debugger at all.
P.S. You just don't want to waste your time and then it will turn out to be closed for security reasons.
What to spend time on? There is no need to write code in DLL now, the speed of language is increased. except for those cases, when it's necessary to address other software modules from MQL
I'm sorry, I guess I'm not articulating it well.
Is there another explanation other than: ...debugging MQL programs with DLLs attached by MetaEditor's built-in debugger?
Hello!
Excuse me, but could you explain more simply what this is all about, because I too would like to be aware of it in case it comes in handy?
For example, what does it mean: "...possibility to debug in DLL..." or "-Give debugging to DLL..." is the same thing or different things?
I think we were talking about the possibility to debug MQL-programs with DLLs attached using MetaEditor's built-in debugger. For security reasons the Developers don't allow it.
How do you understand the expression then?
"We've already conceded once to traders asking "let us debug in DLL" and immediately got EX4 decompiler."
After all, MT4 didn't have a built-in debugger at all.
P.S. I just don't want to waste my time and then find out that it's closed for security reasons.
MT5 has its own debugger, with which you can debug scripts, indicators and Expert Advisors. At least experts can be debugged on weekdays.
We were talking in those posts about the possibility of debugging DLL. Renat noticed that in MT4 (where they didn't have their own debugger) developers made concessions and allowed using external tools for debugging. This eventually led to the creation of ex4 decompilers.
In MT5 the developers took this experience into account and only the built-in debugger can be used, which doesn't allow you to debug a DLL.
The MT5 has its own debugger which can be used to debug scripts, indicators and experts. At least EAs can be debugged on weekdays.
We were talking in those posts about the possibility of debugging DLL. Renat noticed that in MT4 (where they didn't have their own debugger) developers made concessions and allowed using external tools for debugging. This eventually led to the creation of ex4 decompilers.
In MT5 developers took this experience into account and only built-in debugger can be used, which doesn't allow to debug DLL.
Thank you!
Some things seem to be clear now, but could you explain a bit more in detail how it all worked in the first place?
What DLLs are those that cannot be debugged by either the built-in or external debugger?
Thanks!
Some things seem to make sense now, but could you explain a bit more about how it all worked in general?
What DLLs are those that you cannot debug with external or internal debugger?
Although I haven't tried debugging with external debugger myself yet (it worked anyway :) )...
For example MVS has "connect to process" button, may be it was debugged that way when they did it in MT4.
Well, maybe they are talking about dlls written by user (in C++, delphi, etc.) from which functions are imported to MQL5 program...
Although I haven't tried debugging with external debugger myself yet (it worked fine :) )...
For example MVS has "connect to process" button, i guess that's how it worked when i debugged it in MT4.
Thank you!
I think some things make sense now, but could you explain a bit more about how it all worked in general?
What kind of DLL we talking about that you can't debug with external or internal debugger?