Skip to content

std::bad_alloc on windows compiled with mingw-gcc using fmt8

  • can reproduce e.g. by running windows github CI of dune-copasi: test_event_stepper will fail with std::bad_alloc
  • reverting to fmt7 avoids this problem, so for now I'll just do that

output before this error occurs in sme CI:

00:00:00.000 Captured DebugStream dgrave
00:00:00.000 Configuration: backend=default level=critical line_buffered=true
00:00:00.000 Captured DebugStream derr
00:00:00.000 Configuration: backend=default level=error line_buffered=true
00:00:00.000 Captured DebugStream dwarn
00:00:00.000 Configuration: backend=default level=warning line_buffered=true
00:00:00.000 Captured DebugStream dinfo
00:00:00.000 Configuration: backend=default level=notice line_buffered=true
00:00:00.000 Captured DebugStream dverb
00:00:00.000 Configuration: backend=default level=detail line_buffered=true
00:00:00.000 Captured DebugStream dvverb
00:00:00.000 Configuration: backend=default level=debug line_buffered=true

next line of output should be

00:00:00.000 Logging system initialized at Wed 2021-07-14 14:15:40 CEST

so maybe an issue with the date/time formatting somewhere around here?: https://gitlab.dune-project.org/staging/dune-logging/-/blob/master/dune/logging/logging.cc#L531