Code not synced with source
by Mary Westmacott · in Torsion · 06/01/2007 (5:11 pm) · 3 replies
Hi Tom,
This is a really great tool, but a while back the code got out of sync with the source and I can't fix it. I'm using 1.1.53 Beta and TGEA1.01 with DSOs turned off.
Nothing I do seems to fix the problem. I tried creating all new projects, using both debug and release builds of TGEA, clicked 'Sync to editor', tried PreCompiling, and rebuilding exports offen.
It still is allowing me to set a breakpoint on any line, blank lines, comment lines, etc.
Mouse over information seems to works fine. Find in files return the right line number when I search.
But when I hit a breakpoints, but it is obvious from the console messages and the way it skips lines as I step that it is actually executing a dozen line farther down the source file.
What am I doing wrong?
Thank you for such a robust tool.
This is a really great tool, but a while back the code got out of sync with the source and I can't fix it. I'm using 1.1.53 Beta and TGEA1.01 with DSOs turned off.
Nothing I do seems to fix the problem. I tried creating all new projects, using both debug and release builds of TGEA, clicked 'Sync to editor', tried PreCompiling, and rebuilding exports offen.
It still is allowing me to set a breakpoint on any line, blank lines, comment lines, etc.
Mouse over information seems to works fine. Find in files return the right line number when I search.
But when I hit a breakpoints, but it is obvious from the console messages and the way it skips lines as I step that it is actually executing a dozen line farther down the source file.
What am I doing wrong?
Thank you for such a robust tool.
#2
Thank you very much. You seem to hit the nail on the head.
First, Yes I was trying to debug a script in an area following a large /* */ section.
And the TGEA_SDK_Indie-1-0-1.exe install seems to have both of your changes made to the CMDscan.I file. But these changes don't appear in the CMDscan.cpp file.
I patched your changes into CMDscan.cpp and recompiled. I left the /* */ section as it was and now it appears to be setting breakpoints only on valid lines and the code is stepping correctly.
06/04/2007 (9:29 am)
Tom,Thank you very much. You seem to hit the nail on the head.
First, Yes I was trying to debug a script in an area following a large /* */ section.
And the TGEA_SDK_Indie-1-0-1.exe install seems to have both of your changes made to the CMDscan.I file. But these changes don't appear in the CMDscan.cpp file.
I patched your changes into CMDscan.cpp and recompiled. I left the /* */ section as it was and now it appears to be setting breakpoints only on valid lines and the code is stepping correctly.
#3
Thanks for the follow up Mary. I'll make sure the TGEA team are aware of it
06/04/2007 (9:39 am)
Hah... so they patch the .l file, but forgot to rebuild with it... oh so typical. ;)Thanks for the follow up Mary. I'll make sure the TGEA team are aware of it
Associate Tom Spilman
Sickhead Games
I thought this was fixed in TGEA 1.0, but take a look at this old bug fix.