delete invalid pointer message, debugging with preset?

 

Hi,

I posted a similar topic yesterday and actioned a suggestion from Nicholi. However, when debugging again today, I got numerous instances of the "delete invalid pointer" message in the Experts tab, after the debugger inadvertently failed to stop at the first breakpoint. After going through my steps, I noticed that when the indicator dialog loads after pressing the "play" button in the debugger, I was loading a preset file. I did this because recently, I've used preset files in the terminal (I never used them previously) and in a recent round of debugging over the past few weeks have also loaded the same preset file(s) when using the debugger.

I actioned the debugger WITHOUT the preset file and; 1) no problem hitting my initial breakpoint; 2) after quitting the debugger, no "delete invalid pointer" errors in the Experts tab.

I tried this a few times and got the same results. If I don't apply a preset in the debugger, all is well. 

Any thoughts about this?

Cheers!



 
Geester:

Hi,

I posted a similar topic yesterday and actioned a suggestion from Nicholi. However, when debugging again today, I got numerous instances of the "delete invalid pointer" message in the Experts tab, after the debugger inadvertently failed to stop at the first breakpoint. After going through my steps, I noticed that when the indicator dialog loads after pressing the "play" button in the debugger, I was loading a preset file. I did this because recently, I've used preset files in the terminal (I never used them previously) and in a recent round of debugging over the past few weeks have also loaded the same preset file(s) when using the debugger.

I actioned the debugger WITHOUT the preset file and; 1) no problem hitting my initial breakpoint; 2) after quitting the debugger, no "delete invalid pointer" errors in the Experts tab.

I tried this a few times and got the same results. If I don't apply a preset in the debugger, all is well. 

Any thoughts about this?

Cheers!



https://stackoverflow.com/help/mcve
How to create a Minimal, Complete, and Verifiable example - Help Center
How to create a Minimal, Complete, and Verifiable example - Help Center
  • stackoverflow.com
When asking a question about a problem caused by your code, you will get much better answers if you provide code people can use to reproduce the problem. That code should be… …Minimal – Use as little code as possible that still produces the same problem …Complete – Provide all parts needed to reproduce the problem …Verifiable – Test the code...
 
nicholi shen:
https://stackoverflow.com/help/mcve

Short of posting the whole application, I'm not sure what code I could actually post here? The application (indicator) runs and works as expected. If I place a breakpoint in it, anywhere, and run the debugger, it doesn't hit the breakpoint (even the first line) and exits with "deleted invalid pointer" errors in the Experts tab.

This happens after loading a preset before the debugger runs. It's an observation, I don't know why it happens and therefore, I'm at a loss to know what I could post. I've only seen this behaviour since recent updates to MT4. I was hoping that someone had seen this as well.

Thanks anyway.

 

Why open two topics for the same issue?

My workaround would be to put Print statements in front of each delete, to get an idea what pointer is wrong. Maybe it's not even related to your code?

 
lippmaje:

Why open two topics for the same error?

My workaround would be to put Print statements in front of each delete, to get an idea what pointer is wrong. Maybe it's not even related to your code?

It's not the same error, it's the same error message. I updated my code with Nicholi's suggestion. That seemed to work fine. I then noticed the same error when routinely running the debugger after loading a preset file. It's a different post title with an explanation as to the difference. I assume my explanation has been lost on folk.

 
I'd also suggest to narrow down the code and post it here. Maybe you'll find time to add some screenshots, the preset you used and a description of the use case.
 
lippmaje:
I'd also suggest to narrow down the code and post it here. Maybe you'll find time to add some screenshots, the preset you used and a description of the use case.

Cheers and thanks.

Reason: