11-11-2010
Hi,
a fast script solution (but not necessarily fast to run) is to search for some key string where the stack starts or ends? If You can specify such a string, is it data from the the top of the file until some string occurs that You want, or data from that string until the end of file, or data between two known strings?
Best regards,
Lakris
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. SCO
Anyone know how you go about interrogating a panic / core dump with crash for SCO Unix (5 Replies)
Discussion started by: ccarcher
5 Replies
5. 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
6. 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
7. 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
8. 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
9. 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
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 FREEBSD
crashinfo
CRASHINFO(8) BSD System Manager's Manual CRASHINFO(8)
NAME
crashinfo -- analyze a core dump of the operating system
SYNOPSIS
crashinfo [-d crashdir] [-n dumpnr] [-k kernel] [core]
DESCRIPTION
The crashinfo utility analyzes a core dump saved by savecore(8). It generates a text file containing the analysis in the same directory as
the core dump. For a given core dump file named vmcore.XX the generated text file will be named core.txt.XX.
By default, crashinfo analyzes the most recent core dump in the core dump directory. A specific core dump may be specified via either the
core or dumpnr arguments. Once crashinfo has located a core dump, it analyzes the core dump to determine the exact version of the kernel
that generated the core. It then looks for a matching kernel file under each of the subdirectories in /boot. The location of the kernel
file can also be explicitly provided via the kernel argument.
Once crashinfo has located a core dump and kernel, it uses several utilities to analyze the core including dmesg(8), fstat(1), iostat(8),
ipcs(1), kgdb(1), netstat(1), nfsstat(1), ps(1), pstat(8), and vmstat(8).
The options are as follows:
-d crashdir
Specify an alternate core dump directory. The default crash dump directory is /var/crash.
-n dumpnr
Use the core dump saved in vmcore.dumpnr instead of the latest core in the core dump directory.
-k kernel
Specify an explicit kernel file.
SEE ALSO
textdump(4), savecore(8)
HISTORY
The crashinfo utility appeared in FreeBSD 6.4.
BSD
June 28, 2008 BSD