Scribd
Upload
28 views1 page

A.14.3 Temporary Files: Errno Perror

The document discusses implementation-defined behavior regarding temporary files and the errno and perror functions. Specifically, it states that temporary files are removed if a program terminates abnormally. It also notes that errno is set to EBADF (9) by fgetpos or ftell on failure, and describes the messages generated by perror for different errno values.

Uploaded by

Gautam Brown
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
28 views1 page

A.14.3 Temporary Files: Errno Perror

The document discusses implementation-defined behavior regarding temporary files and the errno and perror functions. Specifically, it states that temporary files are removed if a program terminates abnormally. It also notes that errno is set to EBADF (9) by fgetpos or ftell on failure, and describes the messages generated by perror for different errno values.

Uploaded by

Gautam Brown
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Implementation-Defined Behavior [A]

A.14.3 Temporary Files


• Whether a temporary file is removed if a program terminates abnormally
(4.9.4.3).
Temporary files are removed if a program terminates abnormally.

A.14.4 errno and perror


• The value to which the macro errno is set by the fgetpos or ftell
function on failure (4.9.9.1, 4.9.9.4).
errno is set to EBADF (9) by the fgetpos or ftell function on failure.
• The messages generated by the perror function (4.9.10.4).
The message generated is simply a string. The content of the message given
for each legal value of errno is given in the list below, which is of the format
errno_value:message.
1: No permission match (-o32 mode) 1: Not privileged (-n32 and -64
modes)
2: No such file or directory
3: No such process
4: Interrupted system call
5: I/O error
6: No such device or address
7: Arg list too long
8: Exec format error
9: Bad file number
10: No child processes
11: Resource temporarily unavailable
12: Not enough space
13: Permission denied
14: Bad address

007–0701–130 177

You might also like