I migrated a site over to ColdFusion 10, and while I was at it updated Coldbox to V3.5.2 and notice something interesting with line debugging. So to confirm my suspicions I decided to, try both versions to try to narrow down the problem.
And I am not sure I have located it, but I think it is something to do with differences between Coldbox 3.1 and 3.5, and caching.
I am on windows, so can’t confirm or deny if it happens on other configurations, the problem can be duplicated by following these steps.
Place a break point in Application.cfc in the onRequestStart.
Debug application by running debug as
Now with Coldbox 3.1 the line debugger will halt on the line you told it to break on, whereas by replacing the Coldbox version, and restarting the server. Then the next time you try to debug this line, it will not halt.
I first noticed this when trying to debug some modules I am writing for ContentBox, and thought that it might have just been a ColdFusion / Builder problem, that was until I went to do some work on a site using Coldbox 3.1, which allowed the line debugger to work.
Luis, if you’re reading this then I am asking for some help in locating this some more. I am assuming at this stage it is only Coldbox and wish to try to eliminate more variables, if I can. But at this stage, it appears to be Coldbox and caching. I tried to find out how this works in Coldbox 3.5 core files, but I can’t seem to find out how or if they are actually cached.
So if it is not a caching, then maybe something else.
Any thoughts any one?