Re: [ANN] --enable-dbgutil: everyone gets a Debug STL!

On 04/15/2013 03:34 PM, Michael Stahl wrote:
> with commit f14f7a2e4568e3e85a0c8860beebd0376c5a8b51 MSVC builds will
> link everything against the debug runtimes (MSVCRTD etc.), which enables
> debug STL and other things.
[...]
> the MSVC one is tested on MSVC 2008 only, where "make check" passes
> successfully; it's possible that i've overlooked something in the
> makefiles where different MSVC versions use different rules, so it needs
> somebody to try it out in an --enable-dbgutil build with 2010 and 2012.

You probably did that "make check" on a build without any bundled Python 
extensions, right?  In my heavily --enable-ext-* configured build, 
starting soffice instantly fails with

> Fatal Python error: Invalid thread state for this thread
>
> Current thread 0x00000260:
>
> Thread 0x00000260:

on stdout/err and a "Microsoft Visual C++ Debug Library" message box

> Debug Assertion Failed!
>
> Program: C:\lo\core\solver\wntmsci12\installation\opt\program\soffice.bin
> File: f:\dd\vctools\crt_bld\self_x86\crt\src\dbgdel.cpp
> Line: 52
>
> Expression: _BLOCK_TYPE_IS_VALID(pHead->nBlockUse)
>
> For information on how your program can cause an assertion failure, see the Visual C++ 
> documentation on asserts.
>
> (Press Retry to debug the application)

(It would go away if I move 
solver/wntmsci12/installation/opt/share/extensions away and start afresh.)

Stephan