Project

General

Profile

Actions

Emulator Issues #6454

closed

D3D11 broken in Debug builds

Added by NeoBrainX over 11 years ago.

Status:
Fixed
Priority:
Urgent
Assignee:
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Current
Regression:
Yes
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game?
All of them, I guess.

What went wrong?
When trying to run a game with D3D11 on a Debug build, an MSVC debug error message pops up. The error message reads "File: c:\users\tony\desktop\dolphin-emu\source\core\common\src\extendedtrace.cpp
Line: 230

Run-Time Check Failure #2 - Stack around the variable 'dwDisp' was corrupted".

What did you expect to happen?
Stuff working for the single time in a year that I'm doing any development on Windows.

What steps will reproduce the problem?

  1. Select the D3D11 backend
  2. Run a game (or alternatively a fifo log)

What version of Dolphin were you using?
3.5-1716

64 or 32 bit Dolphin?
64 Bit

What version of Dolphin used to work?
I unfortunately have no idea.

What Operating System were you using and what are your hardware
specifications?
Windows 7 x64

Actions #1

Updated by ExtremeDude2 about 11 years ago

I can do some testing if you can give me any idea of where to start :P (i.e. check 3.5+)

Actions #2

Updated by tommyhl2.SS about 11 years ago

3.5-1025 and above all have this issue, so you'll want to look at builds under that number.

Actions #3

Updated by NeoBrainX about 11 years ago

I really have no idea, but it would be highly helpful if you could test this anyway.

If you use intelligent bisecting, you only need to test up to 11 different builds (assuming 3.5 works).

Actions #4

Updated by ExtremeDude2 about 11 years ago

Yeah, I'll start testing when I get home

Actions #6

Updated by ExtremeDude2 about 11 years ago

Well, uh, I just tested latest and it works fine for me

Actions #7

Updated by NeoBrainX about 11 years ago

Uhm, you did use a Debug build, right?

Actions #8

Updated by ExtremeDude2 about 11 years ago

ofc :p, I loaded the project file in MSVS and compiled with f5

Actions #9

Updated by NeoBrainX about 11 years ago

Tried running it in the VS debugger?

Actions #10

Updated by ExtremeDude2 about 11 years ago

Isn't that the whole point of f5?

Actions #11

Updated by NeoBrainX about 11 years ago

You know, I haven't seriously used VS for at least a year... so what do I know :p

Well thanks anyway, guess I'll have to look into the issue on my own...

Actions #12

Updated by ExtremeDude2 about 11 years ago

Sorry I couldn't help

Actions #13

Updated by delroth about 11 years ago

To compile in debug mode you need to change the build configuration to debug. Using F5 does not do that.

Actions #14

Updated by NeoBrainX about 11 years ago

Meanwhile, I get the issue even on 3.5 actually.

Actions #15

Updated by delroth about 11 years ago

That ExtendedTrace.cpp code seems to be broken. Could you try this in ExtendedTrace.cpp:139:

#ifndef _M_X64
DWORD dwDisp;
#else
DWORD64 dwDisp;
#endif

Actions #16

Updated by ExtremeDude2 about 11 years ago

I did set it to build debug as well, in fact that is default anyway is it not? (not that it maters because like I said it was set to debug anyway)

Actions #17

Updated by NeoBrainX about 11 years ago

  • Status changed from New to Fixed

This issue was closed by revision 72abe7c65459.

Actions #18

Updated by delroth about 11 years ago

I want the credits! \o/

Actions

Also available in: Atom PDF