After installing 8.04 all was going very well, but when I put a breakpoint in a certain part of my program, the execution doesn't stop, as if it was not passing there, but I'm 100% sure it passes there.
That breakpoint was within a SUB which definitely gets called. So, I put another breakpoint just on the call statement; the execution does stop there, then I click on "Step into code" button, expecting to end up into the SUB where the the first breakpoint is. Instead, I end up into a different procedure (which is in a different included file); this is a sure thing, no mistakes.
I tried the same, with the very same source and data files, on a second PC, where I hadn't installed the 8.04 update yet, and the problem doesn't occur (the execution just stops on the breakpoint within the SUB as expected).
Then I uninstalled PB/Win from the first PC, reinstalled it and all the updates, up to 8.03 included, and the problem doesn't occur anymore.
The problem occurred 100% of the times, it's not occasional.
However, whether I run this program in the IDE with or without breakpoints, with 8.03 or 8.04, or I run the EXE, there it doesn't seem to be any difference in the actual execution flow, and the output is always the same; the problem seems to be only with debugging.
My best guess is that there is something wrong in my code, which 8.03 kind of forgives but 8.04 doesn't. Memory corruption or something like that.
I know that if I send all the files to PB they could try to help, but it's not that easy, the code is huge, there are lots of includes, hard-coded absolute paths and third parties libraries.
So, before doing that, I'd like to know if someone has any suggestion as to what could I check or do to try to find what in my program could lead to this.
The program has #DIM ALL and #DEBUG ERROR ON at its top. Being a problem with breakpoints, I don't think #TOOLS related statements may help. For what it's worth, I'm checking ERR very very frequently, and at the time of the call to the SUB where the missed breakpoint is, ERR is 0.
That breakpoint was within a SUB which definitely gets called. So, I put another breakpoint just on the call statement; the execution does stop there, then I click on "Step into code" button, expecting to end up into the SUB where the the first breakpoint is. Instead, I end up into a different procedure (which is in a different included file); this is a sure thing, no mistakes.
I tried the same, with the very same source and data files, on a second PC, where I hadn't installed the 8.04 update yet, and the problem doesn't occur (the execution just stops on the breakpoint within the SUB as expected).
Then I uninstalled PB/Win from the first PC, reinstalled it and all the updates, up to 8.03 included, and the problem doesn't occur anymore.
The problem occurred 100% of the times, it's not occasional.
However, whether I run this program in the IDE with or without breakpoints, with 8.03 or 8.04, or I run the EXE, there it doesn't seem to be any difference in the actual execution flow, and the output is always the same; the problem seems to be only with debugging.
My best guess is that there is something wrong in my code, which 8.03 kind of forgives but 8.04 doesn't. Memory corruption or something like that.
I know that if I send all the files to PB they could try to help, but it's not that easy, the code is huge, there are lots of includes, hard-coded absolute paths and third parties libraries.
So, before doing that, I'd like to know if someone has any suggestion as to what could I check or do to try to find what in my program could lead to this.
The program has #DIM ALL and #DEBUG ERROR ON at its top. Being a problem with breakpoints, I don't think #TOOLS related statements may help. For what it's worth, I'm checking ERR very very frequently, and at the time of the call to the SUB where the missed breakpoint is, ERR is 0.
Comment