Does somebody know what this instruction mean?
Oh, I have searched for it already, so no need to ask me to do it again, I just couldn't understand, that's why I'm coming here.
0000000140B39D87 vcvtps2ph xmm2,xmm1,0
0000000140B39D8D vcvtps2ph xmm0,xmm0,0
Related
I have come across a wierd vis studio error which only had one other question I could find that is Similar.
When I try to debug the code I hit run and it says there are errors would I like to run the last working version to which I say no. This then comes up with 91 errors which slowly disappear until there are none left.
This may be quite hard to understand what is actually going on, so I have recorded it to make things a bit easier.
Link to video
I have no idea what is going on and cant seem to find anything other than that other question, which the guy did solve but the next day he turned on his computer the same thing happened, I don't want to be fixing this everyday.
Any Suggestions would be great!
Thanks
All fixed now, I still have no idea what was wrong with it. I just deleted it all and pulled it back down from TFS and it worked, it is a bit of a strange one.
I have had this problem on and off recently with a project I am working on in WPF & C#. The WPF uses an external DLL as an interface written in C++ so its always jumping between managed and unmanaged code (this may or may not be related).
I have found that placing breakpoints and stepping through, sometimes the debugger will just halt and not continue. This is not due to an assert or any other problem because hitting "break" will show the debug cursor at the same line. Just not continuing over it (it happens randomly, anywhere, anytime). This is really frustrating when debugging because the whole debug process has to start again from scratch.
Has anybody come across this and confirm this exists? If so, does anybody have a work around?
Whenever I debug in visual studio my current execution line goes down and then sometimes back up! I thought it was because of some threading issue but its not, I also cannot debug about 70% of the variables, When I hover mouse over a certain variable nothing comes up or it says memory cannot be read, I am desperately trying to solve this, what could be causing this issue?
I hope someone can help, thanks.
I cant get the Graphical Debugger in VS 2012 Ultimate to work, & I have no idea why.
The debugger starts ok, but when I hit the print screen button, the debugger just says its waiting for DX to draw frames. [even after I exit]
I am sure the draw refers to the Present() in the swap chain. I am calling it [thats why you see the box down there]
Is there some bug I need to be aware of?
Edit:
I think the render target might be related to OMSetRenderTargets().
I called it exactly as the SDK sample did, so I don't know what else to think.
I'm a developer on the Visual Studio graphics diagnostic tools at Microsoft. I'm fairly new on the team, and I don't believe that any previous team members were actively watching Stack Overflow, so sorry about the wait on this question.
As it's been a few months I'm guessing that you might not have the repro around anymore. So such this might be a bit hard to diagnose here and now. From what you shared it looks like the playback engine (which we use to capture and replay DirectX data while the application is running) crash while trying to collect data on your application. Sadly with the first release of our tool (In VS 2012) stability issues of this type are more common then we would like. Simply a function of how we did collection on something as complex as DirectX. However since then, particularly with Update 2, we've made some very big strides with compatibility and stability. As a first step I'd make sure that you have all the VS updates installed as Update 2 was a big upgrade for the graphics diagnostic tools in particular (Preview of 2013 as well if you have access to that).
Why don't you use PIX instead http://www.youtube.com/watch?v=-3PISvNTeB0
PIX Tutorial
When using Visual Studio I often encounter situations when the IDE freezes while performing some operation. For instance, this frequently happens when I move next statement pointer (yellow arrow) during the debug session, when I unintentionally press F1, step into some low-level function that has multiple instantiations in the binary code etc.
In these situations Visual Studio notification balloon shows up in the tray with the following text:
Microsoft Visual Studio is Busy
Microsoft Visual Studio is waiting for an internal operation to complete. If you regularly encounter this delay during normal usage, please report this problem to Microsoft.
Often the delay is so long that it is faster to kill the Visual Studio process, start it over again, restart debugging session (or whatever else I was doing) and avoid doing an operation that has caused such a delay. However, this still takes too much time. I would like to have a way to stop/cancel the operation that is taking so much time. For instance, in Total Commander this is possible by pressing Esc during such an operation.
Is something like this possible with Visual Studio? Any plugins that allow doing it? Any other way to circumvent the problem?
P.S. Sorry for the lenghty description, but I wanted to explain the actual problem (not ask if certain solution is possible), so that people can think of ways to solve the problem.
P.P.S. Both 2008 and 2010 suffer from this problem.
If you're debugging, try hitting SHIFT-F5. This should stop the debugger, though probably not immediately, faster than what you've described. The program will process the keyboard a lot faster than trying to click menus with the mouse.
If you're building, try hitting CTRL-Break. Again, it may take a few seconds, but it usually comes around.
I've had the problem you mentioned a few years ago, but I can't remember what I ultimately did to fix it.
There may be many different causes of this issue, but for me apparently what was slowing it down was trying to load symbols from symbol servers. I unchecked the Symbol file (.pdb) locations in the Debugging\Symbols options and the problem went away entirely.
run iisreset may solve your problemstart >> iisreset.exe