I have a trouble with my hardware with Solaris 11 x86. I'll try to debug whats wrong, but I cannot find answer for my question:
I boot my Solaris using Grub, boot_archive loads for 100%, but after kernel crash and machine reboot completely. I need a way how to debug whats exactly wrong with my hardware, f.e. crash dump and freeze with no reboot at all.
From console, run "mdb -K". This will trigger open mdb console, in which, just give ":c" (continue). Now if there is a crash, there won't be a reboot, the console will drop into mdb by printing the stack.
Related
This is a strange one, I've had it occur a few too many times and it's difficult to give a title to, but recently on a number of occasions when I try to open one of my existing sessions (VM or Server doesn't matter) the session doesn't open, it's just a black terminal screen with nothing on it, but my Windows task bar disappears, sometimes it ends up in the MobaXterm terminal window sometimes it doesn't. But if I then try to close the MobaXterm window I get a pop up on my PC for a shutdown, and the only way to close this window is to shut down my PC.
I am running a windows 11 PC, with MobaXterm Home Edition 22.2, and have seen this in 22.1 also. Not sure which earlier versions I was running before I encountered this problem or which version it started with.
Is this a known bug, another of my colleagues has encountered this also? Is there some setup I'm missing that could prevent this?
When I try to run my ubuntu on dusl boot I get message:
/dev/nvme0n1p6: clean, .../.. files, .../... blocks.
How can I repare it or get to my ubuntu?
I have tried to reset it few times and also find on internet some solutions to write something on terminal but in fact I cant get to terminal because I cant launch it. So how can I repare it?
Try to boot into your BIOS. This is on every brand of computer diffrent but most of the time you need to spam press F12, F10, F2.
Once you are booted in Bios you can try to change the default boot drive by the "boot" option.
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
I'm having an issue when attempting to analyze variables in the Eclipse IDE, while in debug mode. At a breakpoint, I'll try to expand a data structure, in the Eclipse variables window, however, the member doesn't display and the program running on the board seems to crash. Once this happens, the only way to reconnect over the jtag is to reboot the board and restart Eclipse.
Without knowing for certain, it seems to be an error with memory allocation in the IDE, but I don't know. Is this a common problem when debugging over jtag? Where might I begin looking to resolve the issue?
I have a jailbroken iPhone 5 running iOS 6.0.1. I installed gdb using pod2g's tutorial here: www.pod2g.org/2012/02/working-gnu-debugger-on-ios-43.html
All of the steps worked, and I copied gdb over to my jailbroken iPhone so I could use it there. gdb starts just fine, but when i try to attach to SpringBoard (or any other running process like Twitter) using
(gdb) attach SpringBoard
this happens:
Attaching to process 7366.
Segmentation fault:11
and I'm returned to the MobileTerminal or ssh prompt (not the gdb prompt). It looks like gdb has crashed, not SpringBoard, because my iPhone does not respring (as it normally does when SpringBoard crashes or is killed). I have tried attaching to SpringBoard using the gdb from the cydia.radare.org source as well, and the exact same thing happens each time. About a week ago, the gdb from the cydia.radare.org source worked just fine, but now both the gdb from pod2g's tutorial and the one from the Cydia source produce the above output. I've tried running gdb as root and the same thing happens. I've googled, and I can't seem to find anything like this. What's wrong and how do I fix it?
Apple has added a PTrace option to prevent debuggers (like GDB) from attaching to processes. Fortunately, you can use GDB to circumvent this as well.
Here is an excellent description:
http://iphonedevwiki.net/index.php/Crack_prevention#PT_DENY_ATTACH