|
|
Sponsored Content
Operating Systems
SCO
SCO 5.07 Panic / Core Dumps
Post 302091457 by ccarcher on Tuesday 3rd of October 2006 06:11:58 AM
10-03-2006
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone know how to read core dumps. Is gdb the only tool for it ? The OS is Solaris.
Thanks (2 Replies)
Discussion started by: suntan
2 Replies
2. Solaris
I have the following set up on a Sun server running solaris 5.8 for core dump generation
coreadm
global core file pattern: /var/core
init core file pattern: /var/core
global core dumps: enabled
per-process core dumps: enabled
global setid core dumps:... (4 Replies)
Discussion started by: handak9
4 Replies
3. Programming
hi everyone,
Right now when I do:
strcmp(s1, s2);
i get a core dump because at times s1 or s2 can be nothing so that makes strcmp() core dump.
What is the solution, if at times I expect one of them (or both) to be NULL?
I want to be able to compare that s1 is NULL and s2 is "blah" or... (6 Replies)
Discussion started by: annie
6 Replies
4. UNIX for Advanced & Expert Users
Hi,
Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB... (2 Replies)
Discussion started by: nsdeeps
2 Replies
5. Programming
My program is not dumping core when hitting a segmentation violation inside a thread.
However, it dumps core when the segv occurs within main.
Any ideas on how to diagnose this?
AIX 5.3 (4 Replies)
Discussion started by: bean66
4 Replies
6. Solaris
i had a situation where a process was defunct. preap would not reap the process and gcore would not work properly (not sure why). therefore, the suggestion was to force a panic and collect the core dump. obviously you could do a savecore -L and capture the dump without bringing down the system.... (3 Replies)
Discussion started by: pupp
3 Replies
7. Ubuntu
Hello,
I am debugging a program which works as daemon. It sigfaults, unfortunately I'm unable to generate core dump file. Here is what I am doing:
tsurko@bastila:~$ ulimit -c unlimited
tsurko@bastila:~$ ulimit -c
unlimited
tsurko@bastila:~$ cat /etc/sysctl.conf | grep 'core_pattern'... (1 Reply)
Discussion started by: tsurko
1 Replies
8. Red Hat
Hi
I have a Fedora installed and I try to generate my application's core dump file.
My system has no coredump limit:
$ ulimit
core file size (blocks, -c) unlimited
But when my application crashes no core dumps generated. I can generate dump file using gcore but it is not appropraite... (1 Reply)
Discussion started by: xyzt
1 Replies
9. Programming
I'm working on a program in Linux with a group of people scattered around the country. When we have a crash, I like to send a core dump to the appropriate person so that they can understand the problem better. The problem is that our application uses several gigabytes worth of data and these... (4 Replies)
Discussion started by: bmsterner
4 Replies
10. HP-UX
kill -SEGV <pid> gives me the core file for that process but also terminates the process.
Can I not get the core dump without terminating the process ? (2 Replies)
Discussion started by: mohtashims
2 Replies
LEARN ABOUT HPUX
dump_concurrent_on
dump_concurrent_on(5) File Formats Manual dump_concurrent_on(5) NAME
dump_concurrent_on - enable/disable option for system to dump memory using multiple dump units when a kernel panic occurs VALUES
Failsafe Default Allowed values Recommended value DESCRIPTION On large systems, the time required to dump system memory when a kernel panic occurs can be excessive or even prohibitive, depending on how much physical memory is installed in the system. Concurrent dump capability results in faster dumps by dividing the task to different dump units which can execute in parallel. The default value for The system determines whether or not to dump with multiple units based on the resources (CPUs and disks) available on the system and the properties of the drivers. The (see crashconf(1M)) command and its associated configuration file control the dump concurrency mode in the memory dumps associated with a system crash. On rare occasions, the system may crash before is run during the boot process. On those occasions, the configuration set using the tunable will be used. Who Is Expected to Change This Tunable? Only HP Field Engineers should change the value of this tunable. Restrictions on Changing Changes to this tunable take effect immediately. When Should the Tunable Be Turned On? This tunable should be turned on to allow dumps to dump with multiple dump units when there is a system crash if there are sufficient resources. What Are the Side Effects of Turning the Tunable Off? Dumps may take more time. When Should the Tunable Be Turned Off? The tunable should be turned off if there is a problem using multiple dump units. What Are the Side Effects of Turning the Tunable On? The system decides whether or not to use multiple dump units based on the resources available. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
crashconf(1M), alwaysdump(5), dontdump(5), dump_compress_on(5). Tunable Kernel Parameters - Integrity Systems Only dump_concurrent_on(5)