Exception in VS2010

Sysprogs forums Forums VisualGDB Exception in VS2010

This topic contains 5 replies, has 2 voices, and was last updated by  DonMilne 1 month ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #20711

    DonMilne
    Participant

    I’m using VisualGDB Custom Edition 5.3, recently renewed support period ending March 2019.

    I typically launch VS2010 by double clicking a shortcut to a .sln file.  For a while now I’ve been getting an error message on startup: “Visual Studio has encountered an exception. This may be caused by an extension. You can get more information by …. etc etc”. The effect is that syntax highlighting and right click “go to definition” etc features are lost in all open text edit windows, however these come back if you close and reopen the file.

    Today I finally decided to investigate the crash. I found that “devenv.exe” ran fine on its own, the error only occurred when I opened a VisualGDB STM32 solution file. When I examined the ActivityLog.xml file I found the following error report:

    When I Googled for this error I find that other people who write VS2010 plugins have encountered the same thing. E.g. discussed here:

    https://social.msdn.microsoft.com/Forums/vstudio/en-US/73253b23-30a5-443e-8a60-e78fa232ce47/activesolutionprojects-comexception-hresult-efail?forum=vsx

    And apparantly it’s caused when a plugin asks for the handle of the solution explorer window and doesn’t check the result. If the solution explorer window is closed or set to auto-hide (as it is in my case) then the returned window handle can be null. It would be nice if this could be fixed.

    • This topic was modified 1 month ago by  DonMilne.
    #20713

    DonMilne
    Participant

    Oh – I forgot to mention that I confirmed that if I run VS2010 and open the solution explorer window before opening the solution, then I don’t get the error.

    #20716

    support
    Keymaster

    Hi,

    No problem, we could add a workaround for this. Please let us know the VisualGDB build number (from the About window) so that we could pinpoint the exact location of the crash.

    #20717

    DonMilne
    Participant

    Hi. It’s VisualGDB 5.3 (build 1836).

    p.s. I had already looked for an update check feature in the software itself. I saw (and tried) the “Upgrade” button but that seems to do something else. I know that devtool packages get occasional automatic updates, but I don’t think that applies to the software itself?

    #20746

    support
    Keymaster

     

    Hi,

    No problem. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2187.msi

    VisualGDB will show the link to a new version once it becomes a stable release. Currently VisualGDB 5.4 is a preview build (i.e. introduces new features, but might be unstable), so we intentionally don’t show it in the update GUI to avoid breaking users who prefer waiting for the stable release.

     

    #20758

    DonMilne
    Participant

    Hi. Sorry for the delay – I had a four day weekend off, and only experienced the problem at work (my home PC has a slightly older VisualGDB build installed).

    I have now tested build 5.4.1.2187 on my work PC and can confirm that it fixed the problem. Thanks!

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.