i am loving these breakdowns. just explanation of how the architecture works from a meaningful context - its so useful. also i love the way you say libraries. thanks for the insight to see that this needed to be explained in this manner.
Could you please explain why you needed to go inside the dynamic libraries to make your cpp program work in your container? What error did you meet? By the way to use the same image do : docker pull clangbuiltlinux/ubuntu Thanks
Sure. When you're docker container - you're using certain distribution of OS, with only few libraries that are available. More complex programs use a lot of libraries, some of them are available as dynamic. In this case I was debugging why postgresql client lib didn't work with my program. I found out that postgres depends on kerberos, which was installed in my system, but in an incompatible version. So now I could either switch the kerberos version or change the version of postgres to match what I had in the system. Other way is providing a directory for dynamic linker to show where your custom versions are, but that's another can of worms.
@@SmokCode Thanks for having provided the context :) I never thought that learning how libraries are used could be so different. Could we say that loading .net libraries are dynamic then?
Wow, I have never heared about most of those things while learning on university or in my first two jobs. If I may ask, did You learn about those things beacause it was needed for specific job or do You just read about those topics in your free time :D
You can use the official reference for PE format (exe, dll and other) docs.microsoft.com/en-us/windows/win32/debug/pe-format I don't know which book is a good one for windows.
