I am trying to debug an application with Immunity debugger. I also tried WinDbg. I have set them as default JIT debugger through the Registry but it doesn`t work.
I tried in Windows XP SP3 and in Windows 7 but it doesn't work.
This might help someone whose immunity debugger does not kick in when the application really crashes like mine.
In regedit, edit the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug
Default: (value not set)
Auto: 1
Debugger: "C:\Program Files\Immunity Inc\Immunity Debugger\ImmunityDebugger.exe" -p %ld
UserDebuggerHotKey: 0
You can install Windbg as the default postmortem debugger by running this from the command line:
windbg -IS
From then on, the next time an application crashes Windbg will appear, attached to the process.
To undo this, see this answer.
If this doesn't work, you'll need to add more details to your question.
If you are using Immunity Debugger, you may want to try to install python 2.7 on your PC.
If it is already installed try reinstalling it
Related
I downloaded the latest ZIP file of VSCode for windows from VSCode website.
Unzipped it and tried running the Code.exe from it. It does nothing no crashing message juts output nothing.
I tried running Code.exe from command prompt [after CD to the directory where I have unzipped it], nothing happens, no out put.
Then I did some googling to do more troubleshooting and found out I need to run Code.exe or bin\code.cmd with --help and --verbose command.
No output on command line.
I am totally confused and don't know how do I make VScode work on my windows 7 machine or how do I troubleshoot why its not working.
I have appropriate .Net Framework installed [the one suggested by the VSCode website].
I have also tried installer , with all above debugging steps , same outcome as above.
I checked the code.exe in task manager to see if its running in background, nothing in there too.
What do I do ?
Check if the process is running in Task Manager.
Check for "code.exe". If it is running, then end all instances, and try again.
Otherwise, try opening event log, in Application or System. Look for errors or warnings which may have been logged and give some insight into why Code didn't open.
So guys seems like new version of VSCode has this problem.
Try downloading an older version of VSCode and do not upgrade it once its installed.
After I installed : V 1.18.1 , its working fine.
I'm using XDebug with Visual Studio Code on Windows 10 to debug PHP.
The debugger works but from time to time it's getting stuck (hits the breakpoint but doesn't respond to step in, step over commands).
I tried switching to XDebug nts version (Not Thread Safe) but it doesn't help. Restarting the web server (Apache) doesn't resolve it either. Sometimes computer restart helps but not always...
Any solution or workaround? (Even a command line that frees this deadlock)
Having out of context debug expressions in the watch window causing the debugger to get stuck.You should clear the watch window from expressions.I guess the evaluation of out of context expressions make the debugger to get stuck.
I've been trying to install gdb to debug using eclipse on my mac with no luck, I followed both of those guides with no success:
https://www.youtube.com/watch?v=JdcpDOf5Sog
[second guide in other comment - can't add more than two links due to new user limitations]
I'm attaching a screenshot to demonstrate:
Gdb "terminated exit value: 0" eclipse on mac
Each time I hit the Debug button I get the same "treminated exit value: 0" error (the code runs perfectly when I hit the run button). Gdb does respond to terminal command "gdb"
I've been researching for quite long and it seems that no one has experienced the same problem I do. (Macbook pro 2016 10.12 Sierra)
I've heard from a friend that I might need to configure my Mac to "developer" mode, I have xcode up and running, but I have no idea what else should I do. Anyway I'm my friend could not guarantee that it is the cause of the problem.
I had issue with terminated exit value: 0 while using older gdb 7.11 because my 7.12.1 does not work on Sierra 10.12.4. There was no solution for my case.
Easy WA is to use LLDB as a debugger for now. Sample instructions here
Another LLDB instruction here
I'm following these instructions to remotely debug a python script http://pydev.org/manual_adv_remote_debugger.html
Using breakpoints and stepping work without a problem, but after resuming the script (without any other further breakpoints) the script executes the remaining instructions, and then hangs instead of exiting normally. Even closing the server from pydev does not help, I have to Ctrl+Break the script
I am sure I've done this a while ago with an older eclipse+pydev, and the script resumed and exited normally (and it's very important for me not to mess the rest of the execution).
I've tried this with both Eclipse Luna and Liclipse pydev_4.0.0.201504132356, pydev_4.0.0.201504092214 on Windows 7 x64, same behaviour
Is this an intended behavior or a bug? How could I make pydev let the script end normally?
I can't reproduce this here... please report that as a bug adding details on how to reproduce it (i.e.: ideally, create a project on github and add a step-by-step on how to reproduce it so that it can be fixed... without being able to reproduce it properly, it may be pretty hard to fix).
Also, please give details on the OS and Python version used in the report (https://sw-brainwy.rhcloud.com/tracker/PyDev/)
I am using nsight eclipse edition for mac to debug my cuda code. I was able to run cuda-gdb all fine from a terminal but was not able to use the debug function in Nsight. Whenever I started to debug, an error window pops up saying "Error in final launch sequence
Connection is shut down". My OS is Mac Lion (10.7.4).
I understand the big thing in Cuda 5.0 is the interactive debugging with eclipse but sadly I won't be able to use it unless I switch to Windows or Linux. If anybody has seen this or knows a workaround for this, please let me know and your help will be very much appreciated.
Thank you!
I'm afraid you've hit a known issue in CUDA 5.0 Toolkit. Due to some last-minute change, cuda-gdb (which is a shell script) is not entirely valid in Mac OS X. To remedy the problem:
Edit cuda-gdb shell script.
Make line #!/bin/sh the first line in this script.
Save the changes
We apologize for inconvenience. This (and many other) issues will be fixed in the upcoming CUDA 5.0 RC release.
I had this problem in linux recently.
Error in final launch sequence Connection is shut down which means nsight can not start debugger correctly.
first you have to make sure you can run cuda-gdb in terminal. just type cuda-gdb in terminal, if it says like cuda-gdb cannot find some lib in /usr/lib, just download or relink it. after you done this , rerun cuda-gdb in terminal, it should work fine. then you can use nsight debugging tool.