crash-dumps

I'm trying to debug a page in a web app that keeps crashing Chrome ("Aw, snap!" error). I've enabled/disabled automatic crash reporting, tried logging with google-chrome --enable-logging --v=1 , (as well as various levels of verbosity), and all I get is a "crash dump ID" in the chrome_debug.log chrome://crashes Shows all of the dump IDs, but no actual dump file I see other questions referring to reading the dump files, but I can't find the dump files themselves (just the ID). Grepping for the crash ID in /tmp and ~/.config/google-chrome/ turns up nothing, but the ~/.config/google-chrome/chrome

A production server has an application running 24x7, and sometimes it starts consuming near 50% of CPU. I couldn't reproduce it locally, but I did a Memory Dump with adplus. The server has Windows 2008 Server 64bits, .NET 3.5. The application listens to a MSMQ and has a thread pool to execute operations, when I did the memory dump it was supposed to be running nothing, but it was still consuming CPU. Below is the Dump. Do you know what can be happening?? It's weird that the slow thread also says GC Disabled! What's that? It's weird I've an ASP.NET app in the same server and sometimes happens

Quick question for you. Will I have any issues with the Appstore approval process if my app periodically checks for crashlogs and uploads it to a server? Is this even possible? If not, can I have something like a global exception handler and make my app terminate gracefully, while being able to upload exception messages to the server? Thanks, Teja For apps distributed through the App Store, Apple will deliver the crash logs to you through iTunes Connect. For Ad-Hoc builds, you will need to have your users send you the crash logs. When the iPhone is synchronized with iTunes, it copies all the

I am working with a legacy VB6/COM application which sometimes causes Windows 7 to crash. I have now generated a .dmp file of one of these crashes using the ProcDump tool from Sysinternals. However, I have never worked with dump files before. Which resources would you recommend for getting started with dump file analysis? Some more links that might be usefull WinDBG and tools: https://developer.microsoft.com/en-us/windows/hardware/download-windbg .Net extension for WinDBG: https://docs.microsoft.com/en-us/dotnet/framework/tools/sos-dll-sos-debugging-extension There are some books such as "

I have an application that sometimes causes a BSOD on a Win XP machine. Trying to find out more, I loaded up the resulting *.dmp file (from C:\Windows\Minidump), but get this message when in much of the readout when doing so: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ******************************************