On Fri, Sep 25, 2020 at 7:58 PM Johannes Schindelin via GitGitGadget <gitgitgadget@xxxxxxxxx> wrote: > > From: Johannes Schindelin <johannes.schindelin@xxxxxx> > > We have some custom handling regarding the link options, which are > specific to each compiler. > > Therefore: let's not just continue without setting the link options when > configuring for a currently unhandled compiler, but error out. > > Note: for some reason, the `invalidcontinue.obj` trick seems not to work > in this developer's hands when building Git in Debug mode: the assertion > dialog that is supposed to be suppressed still pops up, complaining > about the `entry` variable being uninitialized when it is used in > `config.c`'s line 1961. Does this happen when running Git under the Visual Studio debugger? If so this might help _CrtSetReportMode(_CRT_ASSERT,0); After digging a bit more I found out that _CRTDBG_MODE_DEBUG is environment sensitive. It depends on how the debugger handles DbgPrintEx(). Thank You, Sibi Siddharthan
