| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
| |
|
|
|
|
| |
Tsutomu Yamada
|
|
|
|
|
|
|
|
|
|
| |
that memory allocated by starting third party DLLs doesn't end up
conflicting with it.
Hopefully this solves the long-time issue with "could not reattach
to shared memory" errors on Win32.
Patch from Tsutomu Yamada and me, based on idea from Trevor Talbot.
|
|
|
|
| |
provided by Andrew.
|
|
|
|
| |
affected by CloseHandle() or Sleep().
|
|
|
|
|
|
|
| |
it fails because the shared memory segment already exists. This
means it can take up to 10 seconds before it reports the error
if it *does* exist, but hopefully it will make the system capable
of restarting even when the server is under high load.
|
|
|
|
|
|
|
| |
to make sure that the error code is reset, as a precaution in
case the API doesn't properly reset it on success. This could
be necessary, since we check the error value even if the function
doesn't fail for specific success cases.
|
| |
|
|
|
|
|
|
|
|
| |
in the Global\ namespace, because it caused permission errors on
a lot of platforms.
We need to come up with something better for 8.4, but for now
revert to the pre-8.3.4 behaviour.
|
|
|
|
|
| |
* Don't cut off the prefix. With this fix, it's again readable.
* Properly store it in the Global namespace as intended.
|
| |
|
| |
|
|
|
|
| |
ITAGAKI Takahiro
|
|
Uses same underlying tech as before, but not the sysv emulation layer.
|