Unhandled Exception

[12TimesOver]

Task: Selecting Breakpoint in Debug menu
Description: Added a breakpoint in my script, clicked on the breakpoint in the Debug menu to have it take me to the breakpoint in the script
Error: Object reference not set to an instance of an object

Details:

Code: [Select]

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at ៖.៰()
   at ᤬.ᡟᙍ(Object ᙂ, EventArgs ᙄ)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
ScriptUO
    Assembly Version: 0.0.0.0
    Win32 Version: 0.0.0.0
    CodeBase: file:///F:/EasyUO/ScriptUO_v181.exe
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
zip
    Assembly Version: 0.0.0.0
    Win32 Version: 0.0.0.0
    CodeBase: file:///F:/EasyUO/ScriptUO_v181.exe
----------------------------------------
ScriptUO
    Assembly Version: 1.0.3098.33304
    Win32 Version: 0.0.0.0
    CodeBase: file:///F:/EasyUO/ScriptUO_v181.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
ICSharpCode.TextEditor
    Assembly Version: 0.0.0.0
    Win32 Version: 0.0.0.0
    CodeBase: file:///F:/EasyUO/ScriptUO_v181.exe
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.




[TrailMyx]

Heh, well don't do that. 

Really though, breakpoints aren't turned on in v181 other than what I forgot to turn off. 

I'll be posting the breakpoint-enabled version this evening.  I have flushed most of the issues out of it, so if you can break it then I won't be so flippant!

Thanks for the info, though.

[TrailMyx]

BTW, XIIx I'll be adding your name into the About.. box for credit for testing.  I do appreciate it.  No cash, however. 

[12TimesOver]

LOL, no cash necessary I told you I'm psyched to be able to participate, I really think this is a great project!

On the other note, had I paid attention I would have already remembered that I shouldn't be messing with the Breakpoints yet. 

I have another item though, I'll put it here since I'm typing but for future reference, as I find these should I start new threads or try to keep them under a single "issues" thread?

This one is more of a user interface issue and may be by design or something to leave alone based on personal taste but I figured I'd mention it, the Syntax Checker is checking commented code. Not usually a big deal, especially now that I figured out where it was seeing that I was short a bracket (lol, 20 minutes!) but it could be an issue, especially in larger projects.

XII

[TrailMyx]

LOL, no cash necessary I told you I'm psyched to be able to participate, I really think this is a great project!

On the other note, had I paid attention I would have already remembered that I shouldn't be messing with the Breakpoints yet. 

I have another item though, I'll put it here since I'm typing but for future reference, as I find these should I start new threads or try to keep them under a single "issues" thread?

This one is more of a user interface issue and may be by design or something to leave alone based on personal taste but I figured I'd mention it, the Syntax Checker is checking commented code. Not usually a big deal, especially now that I figured out where it was seeing that I was short a bracket (lol, 20 minutes!) but it could be an issue, especially in larger projects.

XII

Well it's all good to know about, even things like this.  With this information, I can try and re-create your crash condition on the much-evolved breakpoint code to be sure that all my changes has eradicated this issue.  I didn't directly address it, but I have pretty much re-written most of that code and finally have spent some time polishing it up.  Since I'm so anal with my source code version control, I can call back the version currently released to verify things, then compile the new version.  I don't even keep backups of the executables.

I noticed that a while back how the pre-parser can pickup on commented code.  I forgot to do anything about it.  The script execution unit skips all comments, but there's a fair amount more logic in that section.  The pre-parser is really some pretty simple code.  It just needs a bit more logic.  But thank you for reminding me; I saw that output from your analysis of Spewy's script.  j4bber had a couple things like that as well.