[Qt-interest] Debugging Crash on Windows

[Tony Rietwyk]

Josiah wrote: 

> I've tried setting a breakpoint on that line and stepping 
> into it - but 
> when I step into it with F11 in the qt creator debugger (qt 
> 4.6.1), it 
> just keeps showing 'operator new' on the stack, and stopping there. 
> Repeated presses of F11 result in 'operator new' staying on top the 
> stack and no change in program position. Pressing F10 (step 
> out) results 
> in program execution halting with the same message ("The inferior has 
> stopped because...SIGSEGV").

Hi, 

I don't know what debugger Qt Creator is using, but in Visual Studio similar
things happen:  

- Stepping INTO 'new ClassName()' steps into the MS new routine
- then you have to step OVER each of the statements in the new routine
- at the end of the new routine, step INTO then takes you to the class
constructor

- continuing to step INTO takes you through:
	- the inherited constructors, if any
	- the initialisation list, if any
	- finally the first statement of the constructor that you wanted. 

- or step OVER skips going through the inherited etc, and goes to the first
statement. 

So it is usually easier to open the constructor source file if possible, and
set a break point there. 

Hope that helps, 

Tony.