coredump

Is there anyway to generate core/heap dump file when JVM crashes? Since these files are usually very helpful to find out bugs in code. Any help is appreciated. cheng Tomasz Nurkiewicz With the following JVM options: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath="/tmp" JVM will dump the content of heap to a file in specified directory. Note that this only happens when OutOfMemoryError is thrown since dump isn't really needed if JVM crashed due to a different reason. Edit: "Boolean options are turned on with -XX:+ and turned off with -XX:-." docs You can use -XX:HeapDump JVM options . 来源：

It looks that OS X (10.6) does not generates codedumps by default. Using the ulimit -c unlimited is not a good solution because ulimit does set the limit in an environment variable. This will work only for console applications executed from the shell that executed ulimit. If you have a gui application this will not work. You can enable core dumps and then launch your GUI app from the command line using open . $ ulimit -c unlimited $ open /Applications/Address\ Book.app I just looked at TN2124 and it suggests a similar approach, only without using open and just launching the app directly, e.g.

I need a way to request a heap dump from within the application . Rationale: When I encounter a specific error condition, I'd like to dump heap, so that I can see what is holding on to the memory. But I would like to automate this (For example, when I detect that some specific condition has occurred. Or when a watchdog doesn't gets its pings anymore. When some test fails). Thus I need a way to dump the heap from within the application itself. I can't seem to find it with the MX beans stuff. Although the MX Beans can give very nice stack traces with monitor and "ownable synchronizer" info,

How can I configure windows to generate a core dump from an application? I'm using Win xp, and the application is build with Visual Studio 2003. Microsoft has a free tool called Userdump.exe which will do this. It's pretty simple to use that tool to create a dump (.dmp) file for a process that shuts down with an exception or to create a dump file for a hanging process Just to throw in some other suggestions: ProcDump that is part of the MS SysInternals suite (it captures crashes but also does a load more, can take dumps if CPU usage spikes for an amount of time, etc) You can put code into your

I have a Python application in a strange state. I don't want to do live debugging of the process. Can I dump it to a file and examine its state later? I know I've restored corefiles of C programs in gdb later, but I don't know how to examine a Python application in a useful way from gdb. (This is a variation on my question about debugging memleaks in a production system .) There is no builtin way other than aborting (with os.abort(), causing the coredump if resource limits allow it) -- although you can certainly build your own 'dump' function that dumps relevant information about the data you

Sometimes when I run my code, a core dump file is generated when I terminate the program by Ctrl + \ . The file name is of the form core.* . The program is not terminating abruptly, and there is no segmentation fault. I believe it is SIGQUIT and not SIGABRT or SIGSEGV . If I try Ctrl + C , or Ctrl + Z , then it is not generated. Can anyone tell why it is generated only when Ctrl + \ is pressed? How can I avoid this core dump file from being generated? Is there any use for the core dumped file? A process dumps core when it is terminated by the operating system due to a fault in the program. The

What is the best way to debug java.lang.OutOfMemoryError exceptions? When this happens to our application, our app server (Weblogic) generates a heap dump file. Should we use the heap dump file? Should we generate a Java thread dump? What exactly is the difference? Update: What is the best way to generate thread dumps? Is kill -3 (our app runs on Solaris) the best way to kill the app and generate a thread dump? Is there a way to generate the thread dump but not kill the app? Analyzing and fixing out-of-memory errors in Java is very simple. In Java the objects that occupy memory are all linked