Timeline for Syscalls required by glibc calls
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 7 at 10:25 | comment | added | Marcus Müller | @PlasmaHH oh if we start taking the shared object mechanism into account, we can give up right there; anything to do with name resolution or user handling might call into NSS or PAM, respectively, including doing things like loading libraries on demand, and these libraries then doing arbitrarily complex things, locally, via network, via shared memory, or pixie dust, that glibc has no knowledge of. | |
| Jul 7 at 10:17 | comment | added | PlasmaHH | It gets further complicated by the symbol versioning mechanism, that is depending on whether the binary that is dynamically linked to requests function@GLIBC_2.4 or @GLIBC_2.12 (or without version) another implementation is used which may in the end call other syscalls | |
| Jul 6 at 15:56 | vote | accept | user30972097 | ||
| Jul 6 at 13:56 | history | answered | Marcus Müller | CC BY-SA 4.0 |