best way to debug nt7 crashes

[e-man]

what is the best way to debug continual nt7 crashes?

CLR Debugger reports this:
An unhandled exception of type 'System.StackOverflowException' occurred in NinjaTrader.Custom.dll

so i know that it's my custom indicator ... crash happens when i apply that indicator to a chart ... but it compiles with no errors; hence the confusion.

i have checked the nt7 logs (in the log directory) and the trace files for zen-fire, but there is no indication of what is breaking or causing the fault.

is there a switch or registry setting to enable more detailed logging?

cheers,
-e

[zweistein]

attach CLR debugger to the NinjaTrader process!
load your .cs file in CLR deb
then compile .cs with debug info in NT7
CLR debugger will ask to reload .cs

then add your indicator to a chart and if there is an exception CLR will trap it and highlight the line in the .cs file

[NinjaTrader_Dierk]

Educated guess: is this an indicator which you did not edit on NS editor? Then you probably have coded an incorrect property like

public double MyProperty
{
    get { return [COLOR=Red][B]M[/B][/COLOR]yProperty; }       // recursive call here
    set { [B][COLOR=Red]M[/COLOR][/B]yProperty = value; }     // recursive call here as well
}

[e-man]

thanks guys! i got the CLR setup, and Dierk you are close ... i did actually edit in the NS compiler, but this is the part of the file where it's breaking:

        public int SignalStop
        {
            get { return iSignalStop; }
            set
            {
                iSignalStop = Math.Max(0, value);
                SignalTrailStop = iSignalStop > 0 ? 0 : iSignalTrailStop;
            }
        }

the property for SignalTrailStop looks similar to SignalStop, just with the second line under set{} reversed.

what i'm trying to achieve here is that if a Stop is specified, it clears out the TrailingStop and visa versa.

based on Dierk's comment about recursion, i changed that second line to read:

iSignalTrailStop = iSignalStop > 0 ? 0 : iSignalTrailStop;

and adjusted the set{} for SignalTrailStop as well.

it compiled and now doesn't throw the error, so many thanks, guys!

not sure if the NS compiler is supposed to detect for recursion, but i might have thrown it off since i was recursively updating another property?

cheers,
-e

[NinjaTrader_Dierk]

Glad it's resolved for you.