Welcome to the MP3Car.com forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Registering will also remove advertisements. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us.

MP3Car.com > Project Tracker Directory > StreetDeck Bug Reports Bug Tracker StreetDeck AV's making Addin debugging impossible

User Name Remember Me? Password

Properties
This is a Critical Unknown / General Bug for 1.1.1.0 of StreetDeck Bug Reports Assigned Flagged for Future Version to Unassigned

marchello2000

01-31-2008 02:55 AM

When running SD under a debugger it will catch every access violation that happens in SD, these are not first chance exceptions, they appear to be completely unhandled (however, SD does not crash which is very strange considering I get all these AV's, perhaps the exceptions are handled somewhere top level (SetUnhandledExceptionFilter?). Anyway, the point is that upon start up and while running SD AV's every second or so making any kind of Addin debugging very impractical. In VS you can't turn off exception break, but NTSD should be able to do that, I haven't tried debugging with NTSD/WinDbg, but naturally I would rather use VS.

god_of_cpu

02-02-2008 06:17 PM

There are exceptions that are by the scripting engine. If an event is not implemented in the script, it will generate a not impleted exception when StreetDeck tries to call it. I'm not sure why your its reporting it as access violation exceptions. There is an exception handler around all COM event calls that will catch all scripting exceptions. I don't currently have a solution for the exceptions generated by the scripting engine, but I will put it in as a feature request to try and look for a solution to not generate exceptions when using the debugger.