---
title: "Discussion on \"5 Things I Check Before Debugging an MQL5 Program\" | Hashnode"
description: "Discussion on \"5 Things I Check Before Debugging an MQL5 Program\". Learn five practical MQL5 debugging techniques, from fixing compiler errors and checking variable types to analyzing runtime logs and testing code"
url: "https://hashnode.com/posts/5-things-i-check-before-debugging-an-mql5-program/6ac9ba3afe6b72a3e60ca95a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [5 Things I Check Before Debugging an MQL5 Program](https://ozdemir.hashnode.dev/5-things-i-check-before-debugging-an-mql5-program?utm_source=hashnode&utm_medium=feed)

Learn five practical MQL5 debugging techniques, from fixing compiler errors and checking variable types to analyzing runtime logs and testing code

Oct 10 · 3 min read · ozdemir.hashnode.dev  
Read the article

-   [#mql5](https://hashnode.com/tag/mql5)
-   [#programing](https://hashnode.com/tag/programing)
-   [#forex](https://hashnode.com/tag/forex)
-   [#forex-trading](https://hashnode.com/tag/forex-trading)
-   [#forex-market](https://hashnode.com/tag/forex-market)
-   [#debugging](https://hashnode.com/tag/debugging)
-   [#metatrader5](https://hashnode.com/tag/metatrader5)
-   [#metatrader4](https://hashnode.com/tag/metatrader4)

## Written by

[Ali Ozdemir](https://hashnode.com/@ozdemir)

@ozdemir · Istanbul, Turkey

  
[View profile](https://hashnode.com/@ozdemir)

MQL5 Developer | Building, Testing & Improving Automated Trading Systems

MQL5 developer focused on building, testing, and improving automated trading software for MetaTrader 5. Open to connecting with developers, traders, and people working on interesting automation projects.

## Responses 1

Markdown supported · ⌘↵ to post

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 10](https://hashnode.com/posts/5-things-i-check-before-debugging-an-mql5-program/6ac9ba3afe6b72a3e60ca95a/comment/6aca407a6e2159d6a6b1422a)

For an EA that compiles, I start with one expected decision and the log from that exact tick. I want the symbol, bar time, inputs, open position and trade return code in the same record. A successful function call alone does not explain whether the trade server accepted the request. Which of those fields do you keep in your first debugging log?
