Note that there are some explanatory texts on larger screens.

plurals
  1. USStephen Kellett
    primarykey
    data
    text
    plurals
    1. COPrincipally for local IPC. I can't remember the details, it was years ago. I think we did briefly look at network stuff as well. But if its poor locally, its probably going to be worse over the network. We did some searches to find if others had problems with named pipes and sure enough they did and no one had a solution, which is why we changed tack completely. The shared memory solution has been great but it has rather tied our software to working on one machine rather than across a network :-(, which fortunately for us, most of our customers want to work on one machine.
      singulars
    2. CO@DeadMG. No compiler warnings. The same code works if called later on in the program lifetime.
      singulars
    3. COMy current thinking is that MS have modified CreateThread so that it examines its callstack and ensures that all locations are tracable back to kernel32.dll/ntdll.dll. If it can't find a valid callstack it assumes the app has been hijacked and denies calls to CreateThread/CreateRemoteThread. In the case that fails for me, the callstack ends at my injected dynamic assembly code that loads my DLL then calls my code. What does anyone think? Is this bonkers or a valid idea to persue? I'm running out of things to try... its going to be very hard to keep a valid callstack doing this stuff.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload