coredump

It seems like I can not generate core dumps in Mac OS X 10.6.8. $ ulimit -c unlimited $ ./a.out Hello world! Segmentation fault $ find ~/ -type f -name core # ls -la /cores/ total 0 drwxrwxr-t@ 2 root admin 68 24 jui 2010 . drwxrwxr-t 31 root admin 1122 17 oct 15:52 .. My current directory, my HOME and /cores/ remain empty… TOC You can generate core dump files on Mac Os X like this: Create the file : /etc/launchd.conf , then : echo "limit core unlimited" | sudo tee -a /etc/launchd.conf Restart your Mac. And that's it, the core dump files are generated in the /cores directory. Be careful the

Every time, my application crash a core dump file is not generated. I remember that few days ago, on another server it was generated. I'm running the app using screen in bash like this: #!/bin/bash ulimit -c unlimited while true; do ./server; done As you can see I'm using ulimit -c unlimited which is important if I want to generate a core dump, but it still doesn't generate it, when I got an segmentation fault. How can I make it work? Make sure your current directory (at the time of crash -- server may change directories) is writable. If the server calls setuid , the directory has to be

I need to store a user's password for a short period of time in memory. How can I do so yet not have such information accidentally disclosed in coredumps or tracebacks? Is there a way to mark a value as "sensitive", so it's not saved anywhere by a debugger? Unknown Edit I have made a solution that uses ctypes (which in turn uses C) to zero memory. import sys import ctypes def zerome(string): location = id(string) + 20 size = sys.getsizeof(string) - 20 memset = ctypes.cdll.msvcrt.memset # For Linux, use the following. Change the 6 to whatever it is on your computer. # memset = ctypes.CDLL("libc

I would like to force a core dump at a specific location in my C++ application. I know I can do it by doing something like: int * crash = NULL; *crash = 1; But I would like to know if there is a cleaner way? I am using Linux by the way. paxdiablo Raising of signal number 6 ( SIGABRT in Linux) is one way to do it (though keep in mind that SIGABRT is not required to be 6 in all POSIX implementations so you may want to use the SIGABRT value itself if this is anything other than quick'n'dirty debug code). #include <signal.h> : : : raise (SIGABRT); Calling abort() will also cause a core dump, and

If a process crashes and leaves a core dump or I create one with gcore then how can I analyze it? I'd like to be able to use jmap , jstack , jstat etc and also to see values of all variables. This way I can find the reasons for a crashed or frozen JVM. Okay if you've created the core dump with gcore or gdb then you'll need to convert it to something called a HPROF file. These can be used by VisualVM, Netbeans or Eclipse's Memory Analyzer Tool (formerly SAP Memory Analyzer). I'd recommend Eclipse MAT. To convert the file use the commandline tool jmap . # jmap -dump:format=b,file=dump.hprof /usr

While running a C program, It says "(core dumped)" but I can't see any files under the current path. I have set and verified the ulimit : ulimit -c unlimited ulimit -a I also tried to find a file named "core", but didn't get the core dumped file? Any help, where is my core file? ephemient Read /usr/src/linux/Documentation/sysctl/kernel.txt . [/proc/sys/kernel/]core_pattern is used to specify a core dumpfile pattern name. If the first character of the pattern is a '|', the kernel will treat the rest of the pattern as a command to run. The core dump will be written to the standard input of that