Sponsored Content
Top Forums Programming Small query regarding function "char * strerror(int errnum)" Post 302762679 by Corona688 on Tuesday 29th of January 2013 01:29:44 AM
Old 01-29-2013
Quote:
Originally Posted by Praveen_218
The primary reason to ask this query is because of the fact that the MAN pages themselves not making me sure if the programmer needs to handle any kind of cleanup post calling strerror()? Just like the call to stat(), lstat(), fstat() which create objects of type struct stat on the heap itself (whose address is returned through the pointer struct stat *sb)
They do no such thing. Pointers do not work that way! You cannot "return an address" through a pointer you pass into a function, any more than you can return a number through a number you pass into a function.

You do not need to clean up after strerror -- or stat, lstat, or fstat, either.
 

8 More Discussions You Might Find Interesting

1. Programming

How to convert the "select" function into a "poll" function

i have a program using the select function but i want to convert it to poll... how can i do this? thanks in advance... :) (1 Reply)
Discussion started by: rbolante
1 Replies

2. UNIX for Dummies Questions & Answers

Explain the line "mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'`"

Hi Friends, Can any of you explain me about the below line of code? mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'` Im not able to understand, what exactly it is doing :confused: Any help would be useful for me. Lokesha (4 Replies)
Discussion started by: Lokesha
4 Replies

3. HP-UX

ERROR: more than one instance of overloaded function "vprintf" has "C" linkage

Hi people! I've got this own library: -------------------------------------------- Personal.h -------------------------------------------- #ifdef __cplusplus extern "C" { #endif #include <stdio.h> #include <stdarg.h> #include <string.h> ... (0 Replies)
Discussion started by: donatoll
0 Replies

4. Solaris

significance of "+" char in SunOS "ls -l" output

Hi, I've noticed that the permissions output from "ls -l" under SunOS differs from Linux in that after the "rwxrwxrwx" field, there is an additional "+" character that may or may not be there. What is the significance of this character? Thanks, Suan (6 Replies)
Discussion started by: sayeo
6 Replies

5. Shell Programming and Scripting

awk command to replace ";" with "|" and ""|" at diferent places in line of file

Hi, I have line in input file as below: 3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL My expected output for line in the file must be : "1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL" Can someone... (7 Replies)
Discussion started by: shis100
7 Replies

6. UNIX for Dummies Questions & Answers

Using "mailx" command to read "to" and "cc" email addreses from input file

How to use "mailx" command to do e-mail reading the input file containing email address, where column 1 has name and column 2 containing “To” e-mail address and column 3 contains “cc” e-mail address to include with same email. Sample input file, email.txt Below is an sample code where... (2 Replies)
Discussion started by: asjaiswal
2 Replies

7. Shell Programming and Scripting

Move a line containg "char" above line containing "xchar"

Okay, so I have a rather large text file and will have to process many more and this will save me hours of work. I'm not very good at scripting, so bear with me please. Working on Linux RHEL I've been able to filter and edit and clean up using sed, but I have a problem with moving lines. ... (9 Replies)
Discussion started by: rex007can
9 Replies

8. Shell Programming and Scripting

Bash script - Print an ascii file using specific font "Latin Modern Mono 12" "regular" "9"

Hello. System : opensuse leap 42.3 I have a bash script that build a text file. I would like the last command doing : print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt where : print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
explain_fstat(3)					     Library Functions Manual						  explain_fstat(3)

NAME
explain_fstat - explain fstat(2) errors SYNOPSIS
#include <libexplain/fstat.h> const char *explain_fstat(int fildes, struct stat *buf); const char *explain_errno_fstat(int errnum, int fildes, struct stat *buf); void explain_message_fstat(char *message, int message_size, int fildes, struct stat *buf); void explain_message_errno_fstat(char *message, int message_size, int errnum, int fildes, struct stat *buf); DESCRIPTION
These functions may be used to obtain explanations for errors returned by the fstat(2) system call. explain_fstat const char *explain_fstat(int fildes, struct stat *buf); The explain_fstat function is used to obtain an explanation of an error returned by the fstat(2) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: if (fstat(fildes, buf) < 0) { fprintf(stderr, "%s ", explain_fstat(fildes, buf)); exit(EXIT_FAILURE); } fildes The original fildes, exactly as passed to the fstat(2) system call. buf The original buf, exactly as passed to the fstat(2) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_errno_fstat const char *explain_errno_fstat(int errnum, int fildes, struct stat *buf); The explain_errno_fstat function is used to obtain an explanation of an error returned by the fstat(2) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (fstat(fildes, buf) < 0) { int err = errno; fprintf(stderr, "%s ", explain_errno_fstat(err, fildes, buf)); exit(EXIT_FAILURE); } errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. fildes The original fildes, exactly as passed to the fstat(2) system call. buf The original buf, exactly as passed to the fstat(2) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_message_fstat void explain_message_fstat(char *message, int message_size, int fildes, struct stat *buf); The explain_message_fstat function may be used to obtain an explanation of an error returned by the fstat(2) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: if (fstat(fildes, buf) < 0) { char message[3000]; explain_message_fstat(message, sizeof(message), fildes, buf); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. fildes The original fildes, exactly as passed to the fstat(2) system call. buf The original buf, exactly as passed to the fstat(2) system call. explain_message_errno_fstat void explain_message_errno_fstat(char *message, int message_size, int errnum, int fildes, struct stat *buf); The explain_message_errno_fstat function may be used to obtain an explanation of an error returned by the fstat(2) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (fstat(fildes, buf) < 0) { int err = errno; char message[3000]; explain_message_errno_fstat(message, sizeof(message), err, fildes, buf); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. fildes The original fildes, exactly as passed to the fstat(2) system call. buf The original buf, exactly as passed to the fstat(2) system call. SEE ALSO
fstat(2) get file status explain_fstat_or_die(3) get file status and report errors COPYRIGHT
libexplain version 0.52 Copyright (C) 2008 Peter Miller explain_fstat(3)
All times are GMT -4. The time now is 11:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy