一维与二维条形码的融合设计

相关报道

• The case of the thread executing from an unloaded third-party DLL

  2.0

  A developer encountered a crash caused by a thread still executing code from a third-party DLL after the DLL had been unloaded. The issue arose because a callback or ongoing operation was not properly canceled before the DLL was freed. The post highlights the dangers of unloading DLLs while threads may still be running code from them.

• I opened a file with FILE_FLAG_DELETE_ON_CLOSE, but now I changed my mind

  1.0

  Once a file is opened with FILE_FLAG_DELETE_ON_CLOSE, the deletion cannot be undone. However, an alternative approach can achieve a similar result without the irreversible flag.

• The case of the DLL that was not present in memory despite not being formally unloaded, part 2

  1.0

  The article describes a debugging scenario where a DLL that was not formally unloaded was nonetheless absent from memory, tracing the root cause to the interaction of two separate bugs in the system's code.

• The case of the DLL that was not present in memory despite not being formally unloaded, part 1

  1.0

  Raymond Chen investigates a mystery where a DLL disappeared from memory without being formally unloaded. The article begins a deep dive into how Windows manages module references, examining possible causes like explicit FreeLibrary calls, reference count issues, or unexpected thread detachments. This first installment sets the stage for diagnosing the missing DLL.

• How did Windows 95 decide that a setup program ran?

  0.5

  Windows 95 used a set of heuristics to determine whether a running program was a setup program. These heuristics included checking file attributes like the presence of a setup logo bitmap or specific version information.