remote-debugging

First let me say that I can remote debug a release build on the remote computer. I set up my release build much like my debug build but I mostly had to make sure the Debug flag was not set. I've dealt with doing this for a while and finally decided to try and figure out why I had to go through this. I should also mention that my remote debugging experience is limited to this project and the C# program uses a C++/CLI (built with /clr) .DLL to mediate to some critical C++ libs. I don't need to debug the underlying C++ libs but I do need to debug the C++/CLI code. (One reason I mention this is I

i am using Spyder 2.3.1 under Windows 7 and have a running iPython 2.3 Kernel on a Rasperry Pi RASPBIAN Linux OS. I can connect to an external kernel, using a .json file and this tutorial: Remote ipython console But what now? If I "run" a script (F5), then the kernel tries to exectue the script like: %run "C:\test.py" ERROR: File u'C:\\test.py' not found. This comes back with an error, ofc, because the script lays on my machine under c: and not on the remote machine/raspberry pi. How to I tell Spyder to somehow copy first the script to the remote machine and execute it there? If I check the

What's the problem? I set up in PyCharm (version 2016.1.4) remote-debugging using the remote interpreter (not Debug Server!) as described here: jetbrains website . When I run in Debug mode the program stops at the break point as it should. But, in the Variables window the variables are not displayed. Instead I get the following Error: Unable to display frame variables I guess this is the same problem: link What did I try? I found this link with a possible solution, but it doesn't work for me. Based on this solution, I modified my helpers/pydev/_pydevd_bundle/pydevd_constants.py file as follows

I can't make source code show in windbg when I pipe ntsd -d on the target through windbg -k , but it works when I debug locally. I want to debug the very first code execution of Winlogon.exe and LSASS.exe. But to make it easy to reproduce the problem, I made up this setup: I use the CrashMe sample application , with source and symbols pre-built, copied to C:\CrashMe on both the target and host I use Windows Debugging tools for Windows (DTW) version 6.12.0002.633 everywhere. The target is running Windows XP SP3, the host Windows 7 ultimate. Every path and settings is the same on both machine :

I can't use normal debugging in Monodevelop , so I am trying to debug remotely as described here . Here is the whole procedure: In a terminal, type: export MONODEVELOP_SDB_TEST="YES" monodevelop & Monodevelop starts. Open your solution Run -> Run With -> Custom Command Mono Soft Debugger Fill the fields: Command: /home/nico/src/CmisSync/bin/SparkleShare.exe Arguments: -debug --debugger-agent=transport=dt_socket,address=127.0.0.1:10000 (not sure if needed) IP: 127.0.0.1 Port: 10000 Output: 1 Press Listen Back to the terminal, press: mono --debug --debugger-agent=transport=dt_socket,address=127

I have a development machine running Windows 7 and Visual Studio 2013. The target framework is .NET 3.5. Now I want to remote debug on a Windows XP system but this seems impossible: msvsmon.exe does not start installing remote tools from http://msdn.microsoft.com/en-us/library/bt727f1t.aspx does not work All I can find from MS is to use VS Studio 2010 Express for debugging. Is there any hack to remote debug in windows xp anyway? Sorry for the inconvenience, but since the remote tools are freely available for each version, we have made the decision that the cost to keep backward compatibility