detailed working of perror

[Innovator]

can anyone please help me out to find out how perror actually works???
In my client.c program i am receiving one error
send: Bad file decriptor
this is printed by perror
as the errno variable is set to 9 which is EBADF
but i want to know from which file does perror seeks or maps this error??
Or more properly how does the kernel maintains the error logs from where the perror prints the latest error.
Please do reply as soon as possible.

[Rubberman]

perror() simply takes the current errno value and output some sort of sensible string. It has nothing to do with error logs, and you are responsible for mapping the error to the file that caused it. Also, EBADF is a bad file descriptor error code, so perror() is simply telling you what you already know...

From the man page for errno:

       EBADF           Bad file descriptor (POSIX.1)
       EBADFD          File descriptor in bad state