I try to do some basic learnings for exploit dev, so I setup a Win XP SP3 machine, installed WinDbg for XP from here:
http://www.codemachine.com/downloads.html
I set Symbols path to:
srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Then I simply start to debug Windows Media Player wmplayer.exe
When I try to show the !peb, I always get the message that my
Debugger is not using the correct symbols.
Any idea ?
Related
Installing Canopy 2.1.9 for Windows 64-bit on Windows 10, and the installer fails immediately after clicking the Install button, with the message "Enthought Canopy (64-bit) Setup Wizard ended prematurely because of an error." Same result using 2.1.8. Same result using the run-as-administrator command line msiexec instructions, same result running the installer as administrator, same result installing for current user or all users.
Enthought support here. Sounds like there's something unusual about your current system status. Most likely would be interference from a 3rd-party anti-virus program, or similar. If temporarily disabling that doesn't help, then please run msiexec /Lv*x canopy-msi.log ... etc..., then zip and send the resulting log, with a link to this SO question, to support#enthought.com. We'll look at it as time permits, though we do not have the bandwidth to help you debug your system setup.
I can't debug my AMP code.
I have:
Visual Studio 2015,
Windows 10 Home 64bit,
GeForce 660 Ti,
DirectX 12
In my C++ project I've set the 'Debugger type' to 'GPU only (C++ AMP)'
The 'Debugging accelerator type' is 'GPU - Software Emulator'
When I try to place a breakpoint in my lambda, I get the "The breakpoint will not be hit...' icon. Also, when I have code that gets the various accelerator infos, they all have 'is_debug=false'--including the 'direct3d/ref' accelerator and the GeForce 660Ti accelerator.
I've also tried specifically setting the default accelerator to direct3d_ref, but of course i think the problem is that it doesn't have debug, anyway.
What gives?
I've got the same situation.
One hint I found: https://msdn.microsoft.com/en-us/library/hh265136.aspx
"Supported Platforms
Debugging is supported on Windows 7, Windows 8, Windows Server 2008 R2, and Windows Server 2012. For debugging on the software emulator, Windows 8, or Windows Server 2012 is required. For debugging on the hardware, you must install the drivers for your graphics card. Not all hardware vendors implement all debugger features. See the vendor documentation for limitations."
From this, I gather that perhaps AMP debugging is not supported on Windows 10. Or perhaps the documentation is out of date.
It makes sense: AMP is made by Microsoft, but Windows 10 is made by Microsoft, so one would not expect them to be compatible. :)
Before I go back to Windows 8.1, I'd like to know for sure....
Another hint for this: When trying to debug I saw a debug output message saying "Please use the /DEBUG:FULL linker switch to hit breakpoints in C++ AMP code."
After changing the linker settings debugging worked for me.
Is your lambda function a c++/amp restricted Function?
It should be so, otherwise the GPU debugging has no permission to enter a c++ restricted code section.
Maybe that is why you get the:
"The breakpoint will not be hit..."
for more information read:
https://msdn.microsoft.com/en-us/library/hh873133.aspx
Of course a code example would be nice.
to try it out on a different machine.
I have compiled and standalone application using MATLAB (32-bit windows 7 ultimate).
even though I have installed MCR of required version on target PC (32-bit windows 7 professional) my application is not working. (installation path C:\Program Files\MATLAB\MATLAB Compiler Runtime)
Note: on other windows 7 Ultimate 32-bit system my application is working fine
That message is indicating that it cannot find the path - I know you said that the path is set correctly.
However I would try setting the PATH variable manually in a dos prompt and then run the exe and see if it will launch.
I'm trying to change the system locale using a PowerShell script, following instructions at
http://technet.microsoft.com/en-us/library/hh825705.aspx#PowerShell.
However, I can't load the international module.
I can't seem to find anything by googling.
I'm using Windows 7 SP1 x64 and PowerShell 3.0.
Where can I find this module (on the local system or for download)?
It's a part of Windows 8/Server 2012 only. see the 'Important' box at the beginning of the post
I'm writing a Kernel mode usb-driver primary for Windows Vista 32bit but hopefully it will also be able to be builded for Win XP, Win Vista, Win 7 32 and 64 bit.
Anyway, I'm debugging from an Windows 7 32bit laptop to a Windows Vista 32bit laptop (the target). The laptops are connected via Firewire and the connection seams to be ok since I can set some breakpoints and step trough parts of my code. All information is in assembly though and WinDbg says "Your debugger is not using the correct symbols..." when I hover over an function in my driver.
Symbol file path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\Me\MyDriver\objchk_wlh_x86\i386
Source file path is:
C:\Me\MyDriver
Everything is newly compiled but WinDgb still won't accept my symbol files. Why?
If you can set breakpoints and step through your code it sounds like your symbols are fine. You can try:
!itoldyouso mydriver
If you want the debugger to convince you that your symbols are OK.
I never use the hover feature in the GUI, but it's entirely possible that it just doesn't work properly in some cases.
-scott