CODEWITHSUNDEEP
delphidebuggingdelphi-2010
James
James

Reputation: 82136

Why does the CPU window always appear when trying to debug my project after a rebuild in Delphi 2010?

Whenever I rebuild my application and try to step into a break-point the CPU window always appears. From what I understand the CPU window appears when DCU does not match up with the source file, however, in my case the DCU's are defintely being re-compiled and there are no old ones lying around or anything like that.

The strange thing here is if I close down the application and re-open the project, place the breakpoint and run it works fine. I can even modify files and just press F9 to run the project and it works fine....it only seems to be when I rebuild the project (via IDE Project menu or the project context menu) that this CPU window never breaks into the source (even though it can find it!).

I also noticed in the callstack a unit called Generics is always the top of the stack, never the unit my break point is in, this is no way related to where my break point is.

Any ideas?

Upvotes: 2

Views: 3695

Answers (2)

Ian Boyd
Ian Boyd

Reputation: 257095

Try checking your Delphi event log.

Sometimes Windows itself will write an OutputDebugString and then trigger a breakpoint when your application has done something very bad, e.g.:

HEAP[Project1.exe]: HEAP: Free Heap block 32959a8 modified at 32959c0 after it was freed
Windows has triggered a breakpoint in Project1.exe.
This may be due to a corruption of the heap, and indicates a bug in Project1.exe or any of the DLLs it has loaded.
The output window may have more diagnostic information

It can also be Application Verifier (if you're using it; if you're not you should) telling you about a problem.

Upvotes: 3

anon
anon

Reputation:

Here I found suggestion to check Ignore non-user breakpoints in Debugger Options (D2009).

Upvotes: 0

Related Questions