4 ms·

>Again, it's purely anecdotal, but I've had more than one topic go without any reply, and one result in a Microsoft employee asking me to email logs. One of whi

>Again, it's purely anecdotal, but I've had more than one topic go without any reply, and one result in a Microsoft employee asking me to email logs. One of which was over 600MB in size, just from loading VS Yes, sometimes to trace down a problem dump files are necessary, and with full heap info they can be big. If you expect psychic debugging based on (often times) vague descriptions of your problems or a problem that they can't repro on their side, then you will be disappointed, then again with expectations like that I imagine you will be disappointed a lot in life from pretty much every software company you ever deal with. >A Microsoft produced and supported VS addon was causing errors in the .NET runtime that were uncaught and untraceable. This sounds...unlikely. Not because Microsoft produced AddOns can't possibly have bugs (of course they can), but saying something is 'uncaught and untraceable' is like saying there is a evil demon in your machine, it just doesn't stand to reason. Exceptions are exceptions are exceptions. Debuggers can and do catch them rather handily, if they didn't / couldn't they would be pretty much useless. I think a more accurate explanation would be 'I couldn't figure out how to diagnose the problem myself'. Without sources that is understandable as often times it is necessary to get to the root of the issue. >Reinstallation of VS, SP1, and all installed version of the .NET runtime were futile So you never solved the issue and continue to see it to this day? Or you just stopped using VS or this particular add-in all together?

drivebyacct2 15y ago
Whatever. I've lost interest in participating in this thread. I don't frankly care if you believe me. The crash occured and the .NET runtime kindly informed me that it was unaware of where the crash was occuring. I'd post it here, but I'd prefer it were not linked to my name as Googling the error message reveals my only post. I had to reinstall Windows to resolve the issue. Reinstalling Visual Studio and the Azure SDK and SP1 and all the .NET runtimes did not resolve the issue. Just so happy to see that I've been downvoted with no explanation to how my comments violated HN principles and I'm being accused of being incompetent and stupid. Fantastic. If I'm so incapable of reproducing issues and "demons in a machine" is so laughable, why exactly does the "Unhandled ExecutionEngineException" exist and why was it more than trivial for me to reproduce? So now three MS people doubting me, mocking me, and suggesting #win32 as remotely comparable to open source style IRC rooms. This is just sad, and ironic as all get out considering the fact that my original comment was that Microsoft and community don't play nice together. Don't you see that irony?
- ryanmolden 15y ago
  >Whatever. I've lost interest in participating in this thread. That's unfortunate. >If I'm so incapable of reproducing issues and "demons in a machine" is so laughable, why exactly does the "Unhandled ExecutionEngineException" exist and why was it more than trivial for me to reproduce? Well, an ExecutionEngineException is simply the CLR encountering some unexpected problem. The CLR is a piece of software like any other, it is simply a COM component, written in C++. Like any other program it too can have bugs and situations that it fails to handle gracefully. They are not untraceable or uncatchable in any way, I have caught and debugged a number of them. Of course without the pdbs/source that is much harder for an external person to do. In my experience it is actually preceded by an SEH exception that the CLR itself will catch and translate into the rather generic ExecutionEngineException, so watching for first chance SEH exceptions is generally more fruitful. >So now three MS people doubting me, mocking me, and suggesting #win32 as remotely comparable to open source style IRC rooms. So when I point out that 'untraceable uncatchable exceptions' don't exist you see that as mocking you? Or was I the doubting one? I am simply a software engineer, like I assume you are. I was pointing out some things don't exist. If untraceable, uncatchable exceptions existed there would be a class of bugs that were logically impossible to find/fix. As for 'the .NET runtime informing you that it was unaware of where the crash was occurring', the .NET runtime would never be aware of such a thing as a crash is a crash. It means the exception found no handler and the process was terminated. Figuring out why is what a debugger is for, not the runtime. >I'd post it here, but I'd prefer it were not linked to my name as Googling the error message reveals my only post. It is strange that you want to hide your identity so much. >This is just sad, and ironic as all get out considering the fact that my original comment was that Microsoft and community don't play nice together. Don't you see that irony? Not really, 'the community' doesn't consist of a single person. I am active on the MSDN forums in my area of expertise. I am also active on my team's blog. In the course of such activities I regularly encounter trolls, I am not saying you are one, just saying they exist. To 'play nice' with a troll is pointless. Some people have axes to grind and no matter what you say or do they will be upset, there is no point trying to help those people. Also, if people are rude from the get-go I tend to not bother helping them, since I generally am spending my own free time to try to help them out, and there are lots of other things I could be doing. Civility is kind of the minbar for what I expect of them. As for 'open source' communities being more civil/friendly...well that is certainly not my experience across the board, but then again, people always have different experiences and tend to remember the worst/most frustrating of them and project that as 'the norm'.

drivebyacct2 15y ago

Whatever. I've lost interest in participating in this thread. I don't frankly care if you believe me. The crash occured and the .NET runtime kindly informed me that it was unaware of where the crash was occuring. I'd post it here, but I'd prefer it were not linked to my name as Googling the error message reveals my only post. I had to reinstall Windows to resolve the issue. Reinstalling Visual Studio and the Azure SDK and SP1 and all the .NET runtimes did not resolve the issue. Just so happy to see that I've been downvoted with no explanation to how my comments violated HN principles and I'm being accused of being incompetent and stupid. Fantastic. If I'm so incapable of reproducing issues and "demons in a machine" is so laughable, why exactly does the "Unhandled ExecutionEngineException" exist and why was it more than trivial for me to reproduce? So now three MS people doubting me, mocking me, and suggesting #win32 as remotely comparable to open source style IRC rooms. This is just sad, and ironic as all get out considering the fact that my original comment was that Microsoft and community don't play nice together. Don't you see that irony?

ryanmolden 15y ago
>Whatever. I've lost interest in participating in this thread. That's unfortunate. >If I'm so incapable of reproducing issues and "demons in a machine" is so laughable, why exactly does the "Unhandled ExecutionEngineException" exist and why was it more than trivial for me to reproduce? Well, an ExecutionEngineException is simply the CLR encountering some unexpected problem. The CLR is a piece of software like any other, it is simply a COM component, written in C++. Like any other program it too can have bugs and situations that it fails to handle gracefully. They are not untraceable or uncatchable in any way, I have caught and debugged a number of them. Of course without the pdbs/source that is much harder for an external person to do. In my experience it is actually preceded by an SEH exception that the CLR itself will catch and translate into the rather generic ExecutionEngineException, so watching for first chance SEH exceptions is generally more fruitful. >So now three MS people doubting me, mocking me, and suggesting #win32 as remotely comparable to open source style IRC rooms. So when I point out that 'untraceable uncatchable exceptions' don't exist you see that as mocking you? Or was I the doubting one? I am simply a software engineer, like I assume you are. I was pointing out some things don't exist. If untraceable, uncatchable exceptions existed there would be a class of bugs that were logically impossible to find/fix. As for 'the .NET runtime informing you that it was unaware of where the crash was occurring', the .NET runtime would never be aware of such a thing as a crash is a crash. It means the exception found no handler and the process was terminated. Figuring out why is what a debugger is for, not the runtime. >I'd post it here, but I'd prefer it were not linked to my name as Googling the error message reveals my only post. It is strange that you want to hide your identity so much. >This is just sad, and ironic as all get out considering the fact that my original comment was that Microsoft and community don't play nice together. Don't you see that irony? Not really, 'the community' doesn't consist of a single person. I am active on the MSDN forums in my area of expertise. I am also active on my team's blog. In the course of such activities I regularly encounter trolls, I am not saying you are one, just saying they exist. To 'play nice' with a troll is pointless. Some people have axes to grind and no matter what you say or do they will be upset, there is no point trying to help those people. Also, if people are rude from the get-go I tend to not bother helping them, since I generally am spending my own free time to try to help them out, and there are lots of other things I could be doing. Civility is kind of the minbar for what I expect of them. As for 'open source' communities being more civil/friendly...well that is certainly not my experience across the board, but then again, people always have different experiences and tend to remember the worst/most frustrating of them and project that as 'the norm'.