Debugging (single stepping and access violations)

"James Hunter" <james.b.hunter@btinternet.com>
18 Jun 2005 23:19:43 -0400

          From comp.compilers

Related articles
Debugging (single stepping and access violations) james.b.hunter@btinternet.com (James Hunter) (2005-06-18)
| List of all articles for this month |

From: "James Hunter" <james.b.hunter@btinternet.com>
Newsgroups: comp.compilers
Date: 18 Jun 2005 23:19:43 -0400
Organization: BT Openworld
Keywords: debug, question

Hi,


I`m not sure this is off-topic for comp.compilers so bear with me :)


I`ve just written BASIC language compiler for Windows, and I`ve ran
into a problem on the debugger.


The debugger uses the windows debug API and so far I`ve got
break-points, debug symbols, resumes, etc. working without too much
hassle - but for single stepping I`ve ran into issues.


After trying tons of ways around this I created a very simple debug
loop (in the debug thread).


While Not Finished
        {
          If WaitForDebugEvent(Blah,0) Then
                  {


ContinueDebugEvent(DebugEvent.dwProcessId,DebugEvent.dwThreadId,DBG_CONTINUE
);
                  EnterSingleStepMode ;
                  }
        }


I monitor (via break-points) the debugeers thread and notice that apps
will (very quickly) EXCEPTION_ACCESS_VIOLATION in what appears to be
'windows' memory range. I`ve even tried notepad.exe, does the same -
so its not my executables.


Does anyone have any ideas at where I could be going wrong? Its driving me
nuts!


Thanks!! James.


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.