Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
Well, I don't think there's anything special that Cygwin does to load
executables, because these are essentially Windows processes, so they are
loaded by Windows, first and foremost.
But it gets even weirder. Below are two _consecutive!_
On 2019-07-09 12:02, Jon Turney wrote:
> On 09/07/2019 17:40, Brian Inglis wrote:
>> On 2019-07-08 12:00, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
>>> Well, I don't think there's anything special that Cygwin does to load
>>> executables, because these are essentially Windows processes
On 09/07/2019 17:40, Brian Inglis wrote:
On 2019-07-08 12:00, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
Well, I don't think there's anything special that Cygwin does to load
executables, because these are essentially Windows processes, so they are
loaded by Windows, first and fore
On 7/9/2019 11:40 AM, Brian Inglis wrote:
> Libraries may be loaded asynchronously as they are accessed, and ldd just
> dumps
> the dll import table once the subprocess is ready to run.
> Perhaps these are import entries that ldd should detect and skip or annotate
> in
> some more useful way.
T
On 2019-07-08 12:00, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
> Well, I don't think there's anything special that Cygwin does to load
> executables, because these are essentially Windows processes, so they are
> loaded by Windows, first and foremost.
>
> But it gets even weirder.
> But it gets even weirder. Below are two _consecutive!_ runs of ldd on the
> very same executable. Why the output differs so drastically (including the
> unknown dlls all of a sudden)?
Another round of consecutive calls of ldd on the very same executable file, and
a similar "indeterministic"
Well, I don't think there's anything special that Cygwin does to load
executables, because these are essentially Windows processes, so they are
loaded by Windows, first and foremost.
But it gets even weirder. Below are two _consecutive!_ runs of ldd on the very
same executable. Why the output
On 2019-07-05 12:28, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
> Here's the output from ldd, of an executable built just recently on Cygwin:
> ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffc339d)
> KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DL
8 matches
Mail list logo
