Does any lock turn off internally?

Question

In Solaris, when I bound dbx to one of the running stacks, did I find a fwrite call leading to __lll_lock_wait ()?

In which scenario will this happen? Does fwrite internally attempt to get a lock?

Answer 1

the standards I looked at (C99 and POSIX) say nothing about locked or unlocked IOs relative fwrite.

On my Linux system, this is not a very accurate reference to page locks man:

   For non-locking counterparts, see unlocked_stdio(3).

and efficiently, there is a function fwrite_unlocked. Standard unlocked function in POSIX - it's just getc_unlocked(), getchar_unlocked(), putc_unlocked()and putchar_unlocked().

, , , IO man (3) IO.

, , , , stderr, .