10 More Discussions You Might Find Interesting
1. Solaris
Hi guys,
just want to know which core file pattern is best to set for core dumps:
1) per-process file name pattern
or
2) global file name pattern.
I will really appreciate an explanation why the chosen one is better.
Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 Replies
2. 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
3. UNIX for Dummies Questions & Answers
my progrme complaints 'Segmentation fault'.
How to let it print 'Segmentation fault(core dumped)' and generate core dump file?
$ulimit
unlimited (22 Replies)
Discussion started by: vistastar
22 Replies
4. SCO
Hello Unix World,
I've been having this issue for the longest time.
Here is my setup
OS: SCO OpenServer 6.0 with mp4, mp3
Server: Dell PowerEdge 840, 800, 2900
USB Stick: Patriot 16GB High Speed, and many other different brands.
Occasinaly while system is running and USB is pluged in the... (0 Replies)
Discussion started by: miles556
0 Replies
5. 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
6. UNIX for Advanced & Expert Users
Hi All,
i am new to this forum.i want detail of reading the core file and trace the problem because of what the program get crashed.please help me.if any body knows any website or tutoril plese let me know.
sudhir (6 Replies)
Discussion started by: sudhir patnaik
6 Replies
7. UNIX for Advanced & Expert Users
Hi,
We have one application (c language) installed on our AIX 5.2. When we enter some large amount of data in one screen and do update, it is dumping core some times without any error (like bus error, segmentation fault). Next we open the application again and enter the same data and do update.... (4 Replies)
Discussion started by: venkatmyname
4 Replies
8. Programming
MY friends:
my program under sco unix have a problem?
it create a core dump file on the path when execute program ,
but i can't find the error of the C program ,i don't know how to
see the error about my program use core, please help me
or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies
9. UNIX for Dummies Questions & Answers
I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start
but savecore failed to create the two files, that is vmcore.n and vmunix.n.
savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname
1)... (4 Replies)
Discussion started by: hassan2
4 Replies
10. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
sys_attrs_ipc(5) File Formats Manual sys_attrs_ipc(5)
NAME
sys_attrs_ipc - attributes for the ipc kernel subsystem
DESCRIPTION
This reference page describes attributes for the Interprocess Communication (ipc) kernel subsystem.
In the following list, attributes whose names are preceded by an asterisk (*) can be modified at run time as well as at boot time.
See sys_attrs(5) for an introduction to system attributes and how to set them.
The maximum number of kernel IPC ports that can be used on the system at one time.
Default value: (task-max * 3 + thread_max) + (thread_max * 2) + 2000
(Values of variables used to establish default value: task_max = nproc +1; thread_max = nproc *2; nproc = 20 + 8 * maxusers)
Do not modify the default setting for this attribute unless instructed to do so by support personnel or by patch kit documentation.
Maximum size, in bytes, of a single System V message.
Default value: 8192 (bytes, which equal 1 page)
Minimum value: 0
Maximum value: INT_MAX
Values for this attribute are restricted by the amount of main memory on the system. The minimum value (0) disables the messaging
system.
Maximum number of bytes that can be queued to a single System V message queue.
Default value: 16,384 (bytes, which equal 2 pages)
Minimum value: 0
Maximum value: INT_MAX
Values for this attribute are restricted by the amount of main memory on the system. The minimum value (0) disables the messaging
system.
Maximum number of System V message queues that can be used on the system at one time.
Default value: 50 (queues) The system rounds the number to the value associated with the next higher power of two; for example, 64.
Minimum value: 0
Maximum value: INT_MAX
Values for this attribute are restricted by the amount of main memory on the system. The minimum value (0) disables the messaging
system.
Maximum number of messages (system wide) that can be queued to System V message queues at one time.
Default value: 40 (messages)
Minimum value: 0
Maximum value: INT_MAX
Values for this attribute are restricted by the amount of main memory on the system. The minimum value (0) disables the messaging
system.
A value that controls the maximum adjustment that can be made to any System V semaphore when a process exits.
Default value: 16,384
Minimum value: 0
Maximum value: 65,536
Maximum number of System V semaphores that can be used on the system at one time.
Default value: 10 (semaphores) (The system rounds the number to the value associated with the next higher power of two; for exam-
ple, 16.)
Minimum value: 0
Maximum value: INT_MAX
Maximum number of System V semaphores that can be used by a single process at one time.
Default value: 25 (semaphores)
Minimum value: 0
Maximum value: INT_MAX
Maximum number of operations that can be outstanding on a single System V semaphore at one time.
Default value: 10 (operations)
Minimum value: 0
Maximum value: INT_MAX
Maximum number of undo operations that can be outstanding on a single System V semaphore at one time.
Default value: 10 (operations)
Minimum value: 0
Maximum value: INT_MAX
Maximum integer value that any System V semaphore can contain.
Default value: 32,767
Minimum value: 0
Maximum value: INT_MAX, but do not enter values higher than 65535
A value that sets default policy for shared memory allocation on NUMA-enabled systems (GS80, GS160, GS320). A value of 1 means that
shared memory is striped across Resource Affinity Domains (RADs). A value of 0 means that shared memory is not striped across RADs.
Default value: 1, for NUMA-enabled systems; 0 for other systems.
Although you can change the value of this attribute while the system is running, there are currently no known situations for which
the shm_allocate_striped value should be changed. A value of 1 is the recommended default policy for all applications on NUMA-
enabled systems. Furthermore, changing the value to 0 on these systems does not override use of striped memory allocation by appli-
cations that explicitly specify and control it through NUMA-specific programming interfaces. Changing the value to 1 on systems that
do not support NUMA has no effect. See numa_intro(3) for an introduction to NUMA.
Disables (0) or enables (1) the dumping of shared memory regions to the core file. The attribute is only used in conjunction with
shared memory.
Default value: 1 (on).
Maximum size, in bytes, of a single System V shared memory region.
Default value: 4,194,304 (bytes) (This value equals 512 pages)
Minimum size, in bytes, of a single System V shared memory region.
Default value: 1 (All requests are rounded to the next page size.)
Maximum number of shared memory regions that can be used on the system at one time.
Default value: 100 (regions) (The system rounds the number to the value associated with the next higher power of two; for example,
128.)
Maximum number of System V shared memory regions that can be attached to a single process at one time.
Default value: 32 (regions)
If enabled (1), writes segmented shared memory contents when an application issues a core dump. If disabled (0), segmented shared
memory is not written to the core dump.
Default value: 1 (enabled)
Because segmented shared memory can be large, the amount of time needed to dump the region to a core file and the amount of file
system space required by the operation can be extensive, especially in large database environments. Therefore, although shared mem-
ory can be useful for debugging, you may not want to include it in core files because of time and resource limitations.
This attribute can be modified at run time.
The minimum size, in bytes, of a System V shared region for the use of shared page tables. Setting this value to 0 disables the
use of shared page tables for shared memory. The size must be at least equal to the value of SSM_SIZE, which is defined in the
machine/pmap.h file (the default is 8 MB).
This attribute can be modified at run time.
Default value: SSM_SIZE
Minimum value: SSM_SIZE
SEE ALSO
sys_attrs(5)
System Configuration and Tuning
sys_attrs_ipc(5)