Unix and Linux Discussions Tagged with crash |
|
Thread / Thread Starter |
Last Post |
Replies |
Views |
Forum |
|
|
|
14 |
13,793 |
Cybersecurity |
|
|
|
3 |
11,902 |
OS X (Apple) |
|
|
|
6 |
17,014 |
AIX |
|
|
|
10 |
22,643 |
OS X (Apple) |
|
|
|
2 |
3,883 |
UNIX for Beginners Questions & Answers |
|
|
|
1 |
2,807 |
Red Hat |
|
|
|
4 |
1,952 |
Solaris |
|
|
|
0 |
1,532 |
Solaris |
|
|
|
2 |
3,285 |
Programming |
|
|
|
2 |
5,027 |
Solaris |
|
|
|
2 |
3,283 |
SCO |
|
|
|
5 |
2,915 |
Solaris |
|
|
|
6 |
3,509 |
SuSE |
|
|
|
4 |
10,335 |
Solaris |
|
|
|
0 |
3,328 |
UNIX for Advanced & Expert Users |
|
|
|
11 |
41,301 |
Linux |
|
|
|
3 |
9,068 |
Solaris |
|
|
|
2 |
7,572 |
Filesystems, Disks and Memory |
|
|
|
4 |
7,019 |
Solaris |
|
|
|
0 |
6,533 |
Linux |
|
|
|
0 |
2,170 |
UNIX and Linux RSS News |
|
|
|
0 |
1,587 |
Complex Event Processing RSS News |
|
|
|
0 |
2,273 |
UNIX and Linux RSS News |
|
|
|
2 |
5,210 |
Red Hat |
|
|
|
0 |
3,118 |
Windows & DOS: Issues & Discussions |
|
|
|
0 |
3,980 |
AIX |
|
|
|
0 |
2,576 |
UNIX and Linux RSS News |
|
|
|
0 |
2,165 |
UNIX and Linux RSS News |
|
|
|
1 |
6,457 |
UNIX for Advanced & Expert Users |
|
|
|
5 |
4,624 |
Shell Programming and Scripting |
|
|
|
0 |
1,228 |
Security Advisories (RSS) |
|
|
|
2 |
3,353 |
UNIX for Advanced & Expert Users |
|
|
|
2 |
4,949 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
3,343 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
7,223 |
UNIX for Advanced & Expert Users |
|
|
|
2 |
4,138 |
Cybersecurity |
|
|
|
2 |
2,945 |
UNIX for Dummies Questions & Answers |
|
|
|
4 |
4,122 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
5,678 |
UNIX for Dummies Questions & Answers |
cr_open(3) Library Functions Manual cr_open(3)
NAME
cr_open() - open crash dump for reading
SYNOPSIS
DESCRIPTION
The library call opens a crash dump and passes back a crash dump descriptor.
The path argument points to a path name naming a crash dump directory or file, and must not exceed bytes in length.
The CRASH * to which crash_cb points is set to a crash dump descriptor, which can then be passed to the other functions to access the crash
dump.
flags is a bitmask of zero or more of the following flag values, which affect the operation of future calls to libcrash routines for this
crash dump, except for cr_verify(3), which has its own flags parameter.
The library will not attempt to verify checksums of files in the crash
dump if this flag is set.
The library will write messages to stderr during time-consuming operations
(decompressions and checksums) if this flag is set.
RETURN VALUE
Returns zero for success. Other possible return values are described in libcrash(5).
EXAMPLES
The following call to opens crash dump contained in the directory and returns the crash dump descriptor For an example of reading the crash
dump see the cr_read(3) manual entry.
AUTHOR
was developed by HP.
SEE ALSO
cr_close(3), cr_perror(3), libcrash(5).
cr_open(3)