coredump

On Mac OS X, if I send SIGQUIT to my C program, it terminates, but there is no core dump file. Do you have to manually enable core dumps on Mac OS X (how?), or are they written to somewhere else instead of the working directory? xyz It seems they are suppressed by default. Running $ ulimit -c unlimited Will enable core dumps for the current terminal, and it will be placed in /cores/ as core.PID. When you open a new session, it will be set to the default value again. On macOS, your crash dumps are automatically handled by Crash Reporter . You can find backtrace files by executing Console and

Is it possible to get gdb or use some other tools to create a core dump of a running process and it's symbol table? It would be great if there's a way to do this without terminating the process. If this is possible, what commands would you use? (I'm trying to do this on a Linux box) DustinB $ gdb --pid=26426 (gdb) gcore Saved corefile core.26426 (gdb) detach Alex Zeffertt Or run gcore $(pidof processname) . This has the benefit (over running gdb and issuing commands to the CLI) that you attach and detach in the shortest possible time. You can used generate-core-file command in gdb to generate

What is SEGV_MAPERR , why does it always come up with SIGSEGV ? There are two common kinds of SEGV , which is an error that results from an invalid memory access: A page was accessed which had the wrong permissions. E.g., it was read-only but your code tried to write to it. This will be reported as SEGV_ACCERR . A page was accessed that is not even mapped into the address space of the application at all. This will often result from dereferencing a null pointer or a pointer that was corrupted with a small integer value. This is reported as SEGV_MAPERR . Documentation of a sort (indexed Linux

My implementation of strcat(char*, const char*) seems to work but then it causes a core dump. strcat() implementation: char* strcat(char* dest, const char* src) { char* tmp = dest; while(*tmp) ++tmp ; while( (*tmp++ = *src++ ) != '\0') ; return (dest); } Code in int main() where I call strcat(): char arr3[] = "Mr. "; char arr4[] = "Smith"; printf("Hello %s!", strcat(arr3, arr4)); It actually concatenated both strings and printed it out but still caused a core dump. output : Hello Mr. Smith!Aborted (core dumped) What did I do wrong? Your program doing buffer overflow at runs time, by strcat

I write this code to read 3 files, TM is the size of square matrix, LER the No. of rows of an array and from last value define a non-square matrix of (ler/2)*2 Then... the code read a file with some relations, all are numbers and are assign to C[ler]. Then ... C[ler] is assigned to B[ler/2][2]. Those coordinates, per row, in B[ler/2][2] are assign to a and b. a and b are the row and the column of the matrix A[tm][tm] where to add 1. My code crashes and I don't see what the error is. When I try to compile it, the compiler gcc -g -o MatSim MatSim.cpp prompted: /usr/include/c++/4.6/iostream:75:

This question already has an answer here: How to generate a core dump in Linux on a segmentation fault? 11 answers I would like to know how to generate a core dump file in Ubuntu. I am using Ubuntu 8.04.1 and gcc compiler 4.2.3. I have written a simple C program to generate a core dump. I have compiled the program as in -- gcc -g badpointer.c . When I run the program its gives segmentation fault but no core dump is generated. What additional things do i have to do to generate a core dump file ? Linux Activate your coredumps by: ulimit -c unlimited Also, check: $ sysctl kernel.core_pattern to

I want a C program to produce a core dump under certain circumstances. This is a program that runs in a production environment and isn't easily stopped and restarted to adjust other kinds of debugging code. Also, since it's in a production environment, I don't want to call abort(). The issues under investigation aren't easily replicated in a non-production environment. What I'd like is for the program, when it detects certain issues, to produce a core dump on its own, preferably with enough information to rename the file, and then continue. void create_dump(void) { if(!fork()) { // Crash the