• Basile B. (3/3) Jul 02 2020 If I compile a debug build with LDC2, targeting amd64 and without
• kinke (5/8) Jul 02 2020 LDC/LLVM generates CodeView for MSVC targets and DWARF for MinGW
• Basile B. (4/12) Jul 02 2020 sounds like what I want, I'll try this.
• kinke (4/6) Jul 02 2020 Nope, it uses the MinGW-*based* libs, where all regular MinGW

Basile B. <b2.temp gmx.com> writes:

If I compile a debug build with LDC2, targeting amd64 and without 
VS installed, does LDC generate debug infos compatible with GDB 
or not ?

kinke <noone nowhere.com> writes:

On Thursday, 2 July 2020 at 07:22:01 UTC, Basile B. wrote:
 If I compile a debug build with LDC2, targeting amd64 and 
 without VS installed, does LDC generate debug infos compatible 
 with GDB or not ?

LDC/LLVM generates CodeView for MSVC targets and DWARF for MinGW 
(...-windows-gnu triples). MinGW isn't fully supported though, so 
unless GDB supports CodeView in the meantime, it probably won't 
work.

Basile B. <b2.temp gmx.com> writes:

On Thursday, 2 July 2020 at 09:43:22 UTC, kinke wrote:
 On Thursday, 2 July 2020 at 07:22:01 UTC, Basile B. wrote:
 If I compile a debug build with LDC2, targeting amd64 and 
 without VS installed, does LDC generate debug infos compatible 
 with GDB or not ?

 LDC/LLVM generates CodeView for MSVC targets and DWARF for 
 MinGW (...-windows-gnu triples).

sounds like what I want, I'll try this.
So in theory when MS toolchain is not installed, LDC uses the 
MinGW libs, so this path should be taken as well.

 MinGW isn't fully supported though, so unless GDB supports 
 CodeView in the meantime, it probably won't work.

kinke <noone nowhere.com> writes:

On Thursday, 2 July 2020 at 10:29:52 UTC, Basile B. wrote:
 So in theory when MS toolchain is not installed, LDC uses the 
 MinGW libs, so this path should be taken as well.

Nope, it uses the MinGW-*based* libs, where all regular MinGW 
extensions/overrides of the underlying MS C runtime have been 
patched out. They cannot be used for ...-windows-gnu targets.