Thread overview
[Issue 14226] invalid Runtime.traceHandler setup
Mar 13, 2015
Ketmar Dark
Oct 24, 2020
Dlang Bot
Oct 24, 2020
Dlang Bot
March 13, 2015
https://issues.dlang.org/show_bug.cgi?id=14226

Ketmar Dark <ketmar@ketmar.no-ip.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ketmar@ketmar.no-ip.org

--- Comment #1 from Ketmar Dark <ketmar@ketmar.no-ip.org> ---
note: it's ok to have it `shared` for GNU/Linux, but it creates initialization cycle for windows.

--
October 20, 2020
https://issues.dlang.org/show_bug.cgi?id=14226

johanengelen@weka.io changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |industry
                 CC|                            |johanengelen@weka.io

--
October 24, 2020
https://issues.dlang.org/show_bug.cgi?id=14226

Dlang Bot <dlang-bot@dlang.rocks> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |pull

--- Comment #2 from Dlang Bot <dlang-bot@dlang.rocks> ---
@kinke updated dlang/druntime pull request #3245 "Fix Issue 14226 - Don't initialize/overwrite global trace handler with each thread" fixing this issue:

- Fix Issue 14226 - Don't initialize/overwrite global trace handler with each thread

  Instead, initialize it once as part of rt_init().

  Keep it as a module ctor instead of manually initializing it in
  rt_init() because `defaultTraceHandler` might depend on other modules
  and their module ctors; that's the case for Windows, where generating a
  trace requires the core.sys.windows.stacktrace module ctor to be run
  first.

https://github.com/dlang/druntime/pull/3245

--
October 24, 2020
https://issues.dlang.org/show_bug.cgi?id=14226

Dlang Bot <dlang-bot@dlang.rocks> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Dlang Bot <dlang-bot@dlang.rocks> ---
dlang/druntime pull request #3245 "Fix Issue 14226 - Don't initialize/overwrite global trace handler with each thread" was merged into master:

- afd2d6bbd678e51cd5794e55fea16b7ab6793ab5 by Martin Kinkelin:
  Fix Issue 14226 - Don't initialize/overwrite global trace handler with each
thread

  Instead, initialize it once as part of rt_init().

  Keep it as a module ctor instead of manually initializing it in
  rt_init() because `defaultTraceHandler` might depend on other modules
  and their module ctors; that's the case for Windows, where generating a
  trace requires the core.sys.windows.stacktrace module ctor to be run
  first.

https://github.com/dlang/druntime/pull/3245

--