Sponsored Content
Full Discussion: core dump file size
Top Forums UNIX for Dummies Questions & Answers core dump file size Post 302130483 by jim mcnamara on Monday 6th of August 2007 10:56:48 AM
Old 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?

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

Core dump in HP-UX..

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

how to view a core dump file

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

core dump

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

How to use a core dump file

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

core dump

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

Cannot generate core dump file

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

Core dump in 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

How to open the core dump file in linux?

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

Problems in reading CORE DUMP file with dbx

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
VOS_SIZE(1)						       AFS Command Reference						       VOS_SIZE(1)

NAME
vos_size - Computes the size of a volume dump SYNOPSIS
vos size [-id] <volume name or id> [-partition <partition name>] [-server <machine name>] [-dump] [-time <dump from time>] [-cell <cell name>] [-noauth] [-localauth] [-verbose] [-encrypt] [-noresolve] [-help] vos si [-i] <volume name or id> [-p <partition name>] [-s <machine name>] [-d] [-t <dump from time>] [-c <cell name>] [-no] [-l] [-v] [-e] [-nor] [-h] DESCRIPTION
The vos size command shows the size of a volume's dump for backup purposes. The size of the dump may differ from the volume size as reported by vos examine or fs listquota. The size is shown in bytes. This command is intended for use with backup systems that want to size volume dumps before performing them (to optimize use of tape resources, for example). OPTIONS
-id <volume name or id> Specifies either the complete name or volume ID number of the read/write, read-only, or backup volume to size. -partition <partition name> Specifies the partition on which the volume resides. Provide the -server argument along with this one. -server <machine name> Specifies the file server machine on which the volume resides. Provide the -partition argument along with this one. -dump Show the size of the volume dump for the specified volume. Currently, this flag should always be given for vos size to give useful information. It is present to allow this command to provide other size estimates in the future. -time <dump from time> Specifies whether the dump is full or incremental. Omit this argument to size a full dump. See vos_dump(1) for the valid values for this option. -cell <cell name> The cell in which the volume resides, if it's not in the current cell. -noauth Assigns the unprivileged identity anonymous to the issuer. Do not combine this flag with the -localauth flag. For more details, see vos(1). -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The vos command interpreter presents it to the Volume Server and Volume Location Server during mutual authentication. Do not combine this flag with the -cell argument or -noauth flag. For more details, see vos(1). -verbose Show more output about what's going on. -encrypt Encrypts the command so that the operation's results are not transmitted across the network in clear text. This option is available in OpenAFS versions 1.4.11 or later and 1.5.60 or later. -noresolve Shows all servers as IP addresses instead of the DNS name. This is very useful when the server address is registered as 127.0.0.1 or when dealing with multi-homed servers. This option is available in OpenAFS versions 1.4.8 or later and 1.5.35 or later. -help Prints the online help for this command. All other valid options are ignored. OUTPUT
When run without -verbose, the output will be: Volume: <volume> dump_size: <size> where <volume> is the name of the volume and <size> is the size of the dump in bytes. With -verbose, additional status messages will be printed between those two lines. EXAMPLES
Sizing a single user volume: % vos size user.thoron -dump Volume: user.thoron dump_size: 36430 or, more verbosely: % vos size user.thoron -dump -verbose Volume: user.thoron Starting transaction on volume 2003434023... done Getting size of volume on volume 2003434023... done Ending transaction on volume 2003434023... done dump_size: 36430 Sizing an incremental dump for the same volume: % vos size -id user.thoron -time '05/04/2007 00:00:00' -dump Volume: user.thoron dump_size: 21095 PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on the machine specified with the -server argument or the machine on which the volume is located if -server was not given. If the -localauth flag is included, the issuer must instead be logged on to a server machine as the local superuser "root". SEE ALSO
fs_listquota(1), vos_dump(1), vos_examine(1) COPYRIGHT
Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com> This documentation is covered by the BSD License as written in the doc/LICENSE file. This man page was written by Jason Edgecombe for OpenAFS. OpenAFS 2012-03-26 VOS_SIZE(1)
All times are GMT -4. The time now is 05:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy