This is what I learn from durian.
Sometimes I get an error while running certain programs, and I wish to help the developer for debugging, what should I send? config.log? screen output? What if successfully compiled the program and when I run the program it gives error? let say segmentation fault. If that is the case, Ican do something as bellow.
1. Generate CoreDumps:
To generate coredumps, I have to set the max core size to unlimited, so the correct coredump file will be generated. I do this:
ulimit -c unlimited
ulimit is a bash utils command, which use to control over the resources available to the shell and to processes started by it. ( I also not really understand what is that.) Anyway you can view all the resources control by typing
2. Run the program.
Run the errornous program, and the coredump file will be generated. The file name usually looks like core.5645. And it can be very large, so it is not possible to send this file.
3. Using gdb to show which file and which line is causing these:
To run gdb with provided coredump file
gdb program-name core-filename
In gdb type
Okay, copy the screen output and send to programmer. To quit gdb, type