Timeline for Why are certain functions from kernel32.dll always imported?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26, 2021 at 22:38 | history | edited | Igor Skochinsky♦ | CC BY-SA 4.0 |
edited title
|
| Sep 25, 2021 at 22:08 | comment | added | 0xC0000022L♦ |
@unc4nny what "Windows compiler"? Several compilers exist for Windows, including Visual C++ from Microsoft, Clang, Intel's compiler and GCC. The compiler runtime and the C runtime are the most likely "culprits" regarding those imports, but you don't give enough details as Igor already tried to point out. Your main() function in a C or C++ is rarely ever identical to the entry point of the binary file. And the part that runs before (and "around") the main() function (aka the runtime) is what influences stuff that seems to be always there.
|
|
| Sep 25, 2021 at 18:48 | answer | added | Igor Skochinsky♦ | timeline score: 4 | |
| Sep 25, 2021 at 17:45 | comment | added | unc4nny | Thanks for the pointers. I will look into the Windows compiler, tho I'm afraid there won't be many resources out there | |
| Sep 25, 2021 at 11:40 | comment | added | Niraeth | The 'standard' imports will vary based on the compiler you use. That said, these are often used by the compiler to perform various things such as handling exceptions (SetUnhandledExceptionFilter, ..) and so on. To see what each function does, you can just go to msdn or any documentation site. If you are looking for a one-page-guide as to why all these functions are imported, you will probably need to look at some sort of pdf/article about how a compiler works internally. | |
| Sep 25, 2021 at 2:20 | answer | added | ismael_akez | timeline score: -1 | |
| Sep 24, 2021 at 17:19 | comment | added | Igor Skochinsky♦ | in what binary? did you inspect all the countless billions of files out there? What else is common among all binaries you've checked? | |
| Sep 24, 2021 at 12:01 | history | asked | unc4nny | CC BY-SA 4.0 |