gflags | gflags package contains a C++ library that implements | Natural Language Processing library

I searched the hard disk for executables containing this word and verifier.exe (application verifier) is the "culprit". After playing with it, it turns out that there is a property for Basics / Heaps with exactly that name:

The functionality probably is:

• recently freed memory will not be given back to heap.
• instead it will be filled with a pattern.
• broken patterns can be used to identify dangling pointers and double frees

So this setting has an impact on the Windows Heap Manager. From the name it's the amount of memory that it holds back for this purpose.

If that registry value is not accompanied by a REG_DWORD VerifierFlags, it probably won't do anything.

Wrote this simple dockerfile.

Dockerfile

what do you mean by only 14 frames ?
do you do enough operations after you enable !htrace for htrace to collect traces ?
as far as i can tell there is no 14 frame limit
just to confirm i attached cdb to a running instance of notepad++ and logged the traces

cdb -pn notepad++
!htrace -enable
.logopen d:\htrace.txt
g
open closed several tabs about , plugins etc to possibly collect
broke back with ctrl+c
did !htrace and quit and awk grepped the htrace.txt

i can see a lot of traces and frames > 14 o a log 1.61 MB big for a few minutes

As your MKL library is installed in /usr/include/mkl location, you can set MKLROOT environment variable as export MKLROOT=/usr/include/mkl Another alternate is, to install oneAPI Base & HPC Toolkits from where you can get Intel MKL library package and initialize oneAPI environment which automatically sets the MKLROOT. For more details regarding oneAPI Base Toolkit and oneAPI HPC Toolkit refer https://software.intel.com/content/www/us/en/develop/articles/installation-guide-for-intel-oneapi-toolkits.html

Refer to the below link regarding Intel oneMKL https://software.intel.com/content/www/us/en/develop/documentation/onemkl-linux-developer-guide/top/getting-started/setting-environment-variables/scripts-to-set-environment-variables.html

This claim

a static library cannot depend on a shared library in Linux

is completely wrong.

A static library is simply a collection of object files.

If you can have code using imports from a shared library that compiles to an .o file, you can collect those .o files into a library and now you have a library that uses imports from a shared library.

The only real difference that a static library makes, compared to linking all the object code directly, is that the library contains an index of symbols that the linker uses to decide which object files inside the library need to be linked. Whereas object files directly passed to the linker are always linked in. This has important ramifications for global initializer behavior and very little else.

Given that an object can be created out of random bytes (so long as alignment requirements are met) it is impossible to say whether some random collection of bytes is of any particular type. Even in the case where there is a value that matches a vtable pointer that is only a very strong hint rather than conclusive proof. After all it would be possible to have an integral member that just happens to have a value that matches the address of a vtable for whatever reason.

Given that reality, I would say it is impossible to even guess at the type of a collction of bytes that do not have a vtable-matching value.

The official answer: "On macOS, x86_64 is the only supported architecture and running Drake under Rosetta 2 emulation on arm64 is not supported." -- https://drake.mit.edu/developers.html#supported-configurations as of 2021-03-18.

You can subscribe to https://github.com/RobotLocomotion/drake/issues/14555 for any updates regarding M1 support.

However, if you want to try to hack through it locally, you could try commenting out homebrew dependencies that do not succeed (e.g., IBEX in this case).

With IBEX disabled, you'll also have to bazel build --define=NO_DREAL=ON to disable dReal for the moment. Likely, other dependencies will also fail, but we have not tested on M1 yet so we don't know how close it is to working.

I've filed https://github.com/dreal/homebrew-dreal/issues/10 in case we can fix the IBEX problem easily.

The other option would be to spin up an Ubuntu VM (based on either 18.04 or 20.04).

I just finished build opencv with android using this :

for ceres

I managed to compile glog on Windows with MinGW using these steps:

in my ceres folder (in my case "D:\INSTALL\Development\lib\ceres-mingw") I typed: