Jump to content
Sign in to follow this  

More technical issues on Windows 10

Recommended Posts

Well, a new KB for 10 has destabilized LotRO on certain platforms.


While I got flamed much for suggesting that SSG open up a support contract with Microsoft to leverage their dev support teams (which is at https://support.microsoft.com/en-us/premier ), because a lot of those engineers can very quickly root cause many of the performance issues that their client faces, and do so a hell of a lot faster than SSG is doing so.

Otherwise, that client will continue to be more screwed as time progresses.

Share this post

Link to post
Share on other sites

Did anybody attach a debugger to get a backtrace?

Does WinBlows even report whether we are looking at a segmentation fault, or an exception, or what here? How do you debug these "didn't work" error messages?

Share this post

Link to post
Share on other sites
21 hours ago, Darmokk said:

That should work on segfaults, right?

How do I get the backtrace out of the dump?

If you need to ask that question, chances are you don't have the capability to actually work with the segfault to figure out what went wrong.

In the actual crash (like, say, Windows  bug checks) the dump file is going to have the error code in the dump file, and that can be seen with WinDbg.  WinDbg is a debugger that's far more powerful than Visual Studio, and less friendly to use than a command prompt, with a learning curve that makes a brick wall look like a down hill ski slope.  If you're actually trying to fix an issue where Windows is bug checking, you're going to need to set up kernel debugging which (again) uses WinDbg and requires two computers.

Also, there's Time Travel Tracing:  https://blogs.msdn.microsoft.com/openspecification/2011/06/28/this-is-how-we-troubleshoot-windows-interoperability-issues-in-the-open-specifications-support-team/

Which can (again) create a file that can be used with WinDbg.

The kicker with all of the debugging stuff: If you don't have the debugging symbols, you will either need to use guesswork and reverse engineer the code, or shelf the project and go do something else with your life.

Also, if you don't heavily work with a debugger day in day out, debugging skill necrosis kicks in and it's kinda sad how fast you lose those skills.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Create New...