08-06-2007
Try instrumenting your code during a couple of test runs:
You can call getrusage() at the end of a run to see the amount of stack and heap memory your program has used. Then you can add the size of the "text" data segment (output of size command).
This sum will be very close to the max core size.
If you are worried only about certain signals causing core, then trap those signals, and in the signal trap call getrusage(). Again we are instrumenting the code.
Remove the instrumentation for production code once you have a handle on the situation.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Dummies Questions & Answers
Hi All
I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
Discussion started by: gyanusoni
0 Replies
3. Programming
by what name does a core dump file stored???
like i wrote a test code:
//dump.c
main()
{
char *p=NULL;
printf("%s",p);
}
of course the above code will produce a segmentation fault. but i cant see any file named core in my CWD. am using SUN0S 5.9 (6 Replies)
Discussion started by: vikashtulsiyan
6 Replies
4. AIX
My application gives core dump. When i am debugging with dbx getting instructions below:
pthdb_session.c, 818: 695445 PTHDB_INTERNAL (internal error)
pthreaded.c, 1941: PTHDB_INTERNAL (internal error)
Illegal instruction (illegal opcode) in . at 0x0
warning: Unable to access address 0x0... (1 Reply)
Discussion started by: bapi
1 Replies
5. Programming
Hi All,
May be it is a stupid question, but, I would like to know what is the advantage using a core dump file at the moment of debugging using gdb.
I know a core dump has information about the state of the application when it crashed, but, what is the difference between debugging using the... (2 Replies)
Discussion started by: lagigliaivan
2 Replies
6. Programming
how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies
7. Shell Programming and Scripting
Segmentation fault(core dumped)
but I cant find core file any where. how to make it out?
I try the command:ulimit -c unlimited, I even added it to the .bashrc file.And I removed ulimit setting in /etc/init.d/function. And there's no ulimit setting in /etc/profile. And I tried sudo find /... (8 Replies)
Discussion started by: vistastar
8 Replies
8. HP-UX
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Discussion started by: messi777
1 Replies
9. Emergency UNIX and Linux Support
Hi,
I have got core dump stating "core.bash.29846" so i am unable to open.
How to open the core dump file for further analysis?
Reagards
Vanitha (7 Replies)
Discussion started by: vanitham
7 Replies
10. Solaris
I am new to UNIX.
My Application is using c (.so files) and Java code.
My application crashes and CORE DUMP file is generated ,which is huge.
Now I want to view the CORE DUMP file to debug the application using dbx without starting process again.
By only using the CORE DUMP file and dbx ,can i... (1 Reply)
Discussion started by: satde
1 Replies
LEARN ABOUT FREEBSD
savecore
SAVECORE(8) BSD System Manager's Manual SAVECORE(8)
NAME
savecore -- save a core dump of the operating system
SYNOPSIS
savecore -c [-v] [device ...]
savecore -C [-v] [device ...]
savecore [-fkvz] [-m maxdumps] [directory [device ...]]
DESCRIPTION
The savecore utility copies a core dump into directory, or the current working directory if no directory argument is given, and enters a
reboot message and information about the core dump into the system log.
The options are as follows:
-C Check to see if a dump exists, and display a brief message to indicate the status. An exit status of 0 indicates that a dump is
there, 1 indicates that none exists. This option is compatible only with the [-v] option.
-c Clear the dump, so that future invocations of savecore will ignore it.
-f Force a dump to be taken even if either the dump was cleared or if the dump header information is inconsistent.
-k Do not clear the dump after saving it.
-m maxdumps Maximum number of dumps to store. Once the number of stored dumps is equal to maxdumps the counter will restart from 0.
-v Print out some additional debugging information. Specify twice for more information.
-z Compress the core dump and kernel (see gzip(1)).
The savecore utility looks for dumps on each device specified by the device argument(s), or on each device in /etc/fstab marked as ``dump''
or ``swap''. The savecore utility checks the core dump in various ways to make sure that it is complete. If it passes these checks, it
saves the core image in directory/vmcore.# and information about the core in directory/info.#. For kernel textdumps generated with the
textdump(4) facility, output will be stored in the tar(5) format and named directory/textdump.tar.#. The ``#'' is the number from the first
line of the file directory/bounds, and it is incremented and stored back into the file each time savecore successfully runs.
The savecore utility also checks the available disk space before attempting to make the copies. If there is insufficient disk space in the
file system containing directory, or if the file directory/minfree exists and the number of free kilobytes (for non-superusers) in the file
system after the copies were made would be less than the number in the first line of this file, the copies are not attempted.
If savecore successfully copies the kernel and the core dump, the core dump is cleared so that future invocations of savecore will ignore it.
The savecore utility is meant to be called near the end of the initialization file /etc/rc (see rc(8)).
SEE ALSO
gzip(1), getbootfile(3), textdump(4), tar(5), dumpon(8), syslogd(8)
HISTORY
The savecore utility appeared in 4.1BSD.
Support for kernel textdumps appeared in FreeBSD 7.1.
BUGS
The minfree code does not consider the effect of compression or sparse files.
BSD
December 17, 2012 BSD