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
Related
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 ?
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.
Currently I'm trying to run Eclipse Classic under Windows 7 x64, without success.
First, I've downloaded the JDK from here.
Second, I've downloaded the Eclipse 32 bit Version, which crashes while showing the splashscreen, for a very short time.
The 64 bit version at last, shows an error message, that the jvm.dll can't be loaded (shown path is valid).
What can I do now? Java seems to work, as I can run Netbeans and other Java Applications.
I also have no error log of Eclipse, as no workspace is setup.
Fixed it! For both, 32 & 64 Bit version. I used the posted Eclipse.ini setting from here, edited the paths to fit my environment and bam! It worked. Thanks for your support :)
Make sure you're running a 64 bit JDK, that JAVA_HOME is set properly, and that %JAVA_HOME%\bin is in the front of your path. I also might try running eclipse from the DOS prompt to see if you get any startup error info there.
I just got this MSI wind netbook and tried to run eclipse on it. I installed JDK6 on the netbook already. Whenever I open eclipse there is nothing show up on the screen except a "warning sound" that alerts. What is the problem here?
ps.I just started learning java.
Most likely the Eclipse starter program can't find where you installed Java. Since Eclipse is a Java program, it needs a JRE installed (comes with the JDK typically) to run. Assuming you're running Windows on your MSI Wind, check to make sure the java executable is on your path in your computer environment settings (windows key + printscreen button, or windows key + pause button are the shortcuts to open the computer properties dialog if I remember correctly. Then go to advanced).
You can test if java is on the path by opening a cmd.exe shell window and typing 'java'. If it says it cannot find java, then you need to fix the path.
See this link for additional troubleshooting details: http://www.eclipsezone.com/eclipse/forums/t99010.html
You could try reinstalling the JDK. Perhaps having it on a different disk than the default (D: versus C:) is causing some trouble? It certainly isn't a problem with the hardware, I'm running Eclipse on Windows on an MSI Wind.
Use "Add/Remove programs" in the control panel to remove the java versions you have installed.
Then visit "java.com" and use it to install Java, and verify that it is working. You do not need more than that to use Eclipse.
I was wondering if anyone has successfully ran Nant on Windows Vista 64 bit version. It keeps failing with
set-props:
[sysinfo] Setting system information properties under sys.*
BUILD FAILED
Property name 'sys.env.CommonProgramFiles(x86)' is invalid.
Yes, it works. NAnt is by default built for 32-bit. Therefore, one has to remember to run this in a 32-bit command prompt or PowerShell. I run NAnt scripts out of PowerShell (x86) mode on a Vista 64 machine, but an SDK prompt (32-bit) would works as well.
It also has worked well for me. I do run as Scott said in a 32bit command prompt.
It could also be just a specific thing you are trying to capture that nAnt is not expecting.
I've been using NAnt on my Windows 7 64 bit environment, and have found that in order to do so (without needing to use a 32bit command environment) is to simply remove the reference in your NAnt scripts to sysinfo.
I have been through our build scripts over and over and cannot see any downside to removing this setting, as I cannot prove that I'm using the result of it anyway, other than to dump lots of data to the screen which is invaluable during debugging!!
Hope this helps!