body { -ms-overflow-style: scrollbar; overflow-y: scroll; overscroll-behavior-y: none; } .errorContainer { background-color: #FFF; color: #0F1419; max-width: 600px; margin: 0 auto; padding: 10%; font-family: Helvetica, sans-serif; font-size: 16px; } .errorButton { margin: 3em 0; } .errorButton a { background: #1DA1F2; border-radius: 2.5em; color: white; padding: 1em 2em; text-decoration: none; } .errorButton a:hover, .errorButton a:focus { background: rgb(26, 145, 218); } .errorFooter { color: #657786; font-size: 80%; line-height: 1.5; padding: 1em 0; } .errorFooter a, .errorFooter a:visited { color: #657786; text-decoration: none; padding-right: 1em; } .errorFooter a:hover, .errorFooter a:active { text-decoration: underline; } #placeholder, #react-root { display: none !important; } body { background-color: #FFF !important; }

JavaScript is not available.

We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using twitter.com. You can see a list of supported browsers in our Help Center.

Help Center

Conversation

Daniel Feichter

@VirtualAllocEx

Jun 2

A question about the transition from Win32 APIs to NTAPIs. When debugging a Win32 API like VirtualAlloc with x64dbg I can see the following path from calling the Win32 API to executing the syscall. .exe -> kernel32.dll -> kernelbase.dll -> ntdll.dll So my questions are: - Why… Show more

namazso

@namazso

Legacy. That's what the library name was in Win9x so it must stay. They could move all code in the OS into a single dll, and you'd still have the stub dlls so that the LoadLibrary+GetProcAddress from 25 years ago still works. That's it.

8:47 AM · Jun 2, 2023

422

Views

Likes