crash-dumps

Whats the main advantage and disadvantage of “do not keep activities” in android

萝らか妹 提交于 2019-11-30 01:47:06
One query I would like to have if anyone could answer it like: Do not keep activities options to be checked during testing android mobile application from developers options. I used it in my application and found that my application behaves inappropriately and crashed when I switched ON Do not keep activities in android. My questions were few : 1: How much this option will affect mobile applications? 2: What exactly does this do? It sounds like an app killer,I notice in the Developer Options there is a box that says Do not keep activities - destroy every activity as soon as the user leaves it

minidump vs. fulldump?

此生再无相见时 提交于 2019-11-30 01:15:22
I just recently started looking at dump files to help me analyze crashes of the w3wp process on our production environment at work... And I would like to know, what are the differences between a minidump and a fulldump file ? foxy Differences between full memory dump files and mini memory dump files A memory dump file can collect a variety of information. Typically, a support engineer must have all the contents of virtual memory to troubleshoot a problem. In other cases, you might want to capture less information to focus on a specific problem. The debugger is flexible. This flexibility lets

A process crashed in windows .. Crash dump location

最后都变了- 提交于 2019-11-29 22:21:23
A windows process got crashed for some reason. I need to analyse the crash dump. In Windows 2003 PC health helped us to find the crash dump file. How to get the crash dump file location in Windows 2008? I have observed on Windows 2008 the Windows Error Reporting crash dumps get staged in the folder: C:\Users\All Users\Microsoft\Windows\WER\ReportQueue Which, starting with Windows Vista, is an alias for: C:\ProgramData\Microsoft\Windows\WER\ReportQueue Kiquenet Maybe useful (Powershell) http://sbrennan.net/2012/10/21/configuring-application-crash-dumps-with-powershell/ From Windows Vista and

Application.ThreadException vs AppDomain.UnhandledException

↘锁芯ラ 提交于 2019-11-29 13:12:28
问题 First some background: I have a multi-threaded WinForms application that is doing interop to native dlls. This application crashes sometimes with unhandled exception and we are trying to investigate why does it happen. In order to facilitate it, I am creating a global exception handler and I plan to generate process dumpfile from it. Now coming towards question: as of now this application has handler for Application.ThreadException but it still crashes with unhandled exception. I am thinking

Symbol issue when debugging C# code

杀马特。学长 韩版系。学妹 提交于 2019-11-29 05:23:11
I am using WinDbg to load a crash dump from managed code (C#, a console application built for Any CPU ), and a crash dump is created on a x64 platform. I am debugging on a x64 platform. I have put the related PDB file into the symbol path. But WinDbg always find the symbol from a strange folder. Here is an example (when I got from using !sym noisy): SYMSRV: c:\MySymbols\FooService.pdb\4311207E2E2D442CB7473828D2488F941\FooService.pdb not found My application is called FooService.exe and the related PDB file is named FooService.pdb . I have set C:\MySymbols as the symbol path and copied

How to list call stack of all managed threads using WinDBG?

倾然丶 夕夏残阳落幕 提交于 2019-11-29 01:42:49
问题 I have a dump created from a managed application. I am using SOS/SOSEX extentions to ease my dump analysis. I'd like to list down the call stack of all managed threads as we do ~*kb with native applications. How do we do that? 回答1: Use the sos !EEStack command: 0:007> .load sos 0:007> !EEStack See SOS.dll (SOS Debugging Extension) 回答2: This command will dump all managed threads ~*e!dumpstack 回答3: with sosex, use ~*e!mk (~ - thread, * - all, e - execute this command, !mk - display managed

Is it possible to specify where JVM's crash dumps go?

杀马特。学长 韩版系。学妹 提交于 2019-11-28 21:30:56
We have a desktop application using JNI that occasionally causes the JVM to crash. Luckily the JVM produces a hs_err_pidXXXX.log file, which is quite useful in debugging such errors. However, it always seems to go to the current working directory, and it's annoying to dig it from there, since our other log files all go to a specific "log file place". Is it possible to specify different location for those "crash dump" files? How? Joonas, Although the HeapDumpPath works for the heap dump it is not the answer for your question. The heap dump and the jvm crash log are two separate things. To

minidump vs. fulldump?

蓝咒 提交于 2019-11-28 20:52:11
问题 I just recently started looking at dump files to help me analyze crashes of the w3wp process on our production environment at work... And I would like to know, what are the differences between a minidump and a fulldump file ? 回答1: Differences between full memory dump files and mini memory dump files A memory dump file can collect a variety of information. Typically, a support engineer must have all the contents of virtual memory to troubleshoot a problem. In other cases, you might want to

how to generate thread dump java on out of memory error

。_饼干妹妹 提交于 2019-11-28 18:56:57
does java 6 generate thread dump in addition to heap dump (java_pid14941.hprof) this is what happened to one of my applications. java.lang.OutOfMemoryError: GC overhead limit exceeded Dumping heap to java_pid14941.hprof ... I did find ava_pid14941.hprof in working directory, but didn't find any file which contains thread dump. I need to know what all the threads were doing when I got this OutOfMemory error. Is there any configuration option which will generate thread dump in addition to heap dump on out of memory exception? How to generate thread dump java on out of memory error? Your question

Analyzing Crash dumps in Visual Studio

不羁的心 提交于 2019-11-28 09:53:19
I have a *.dmp (dump) file of my crashed application. Now, I want to analyze the crashed process on a different machine. That is, the app crashed on one machine, and I have Visual Studio on other machine. Now, what do I need to be able to see stack trace and all symbols of my app? Is *.exe file and the *.dmp file sufficient? Or do I need also the source code and PDB file? If so, should the source code and executable file be placed in the same directories structure as it is on the machine the process was running? How to attach PDB file to crash dump file in Visual Studio? No, you definitely