On Monday, 30 May 2016 at 06:39:38 UTC, chmike wrote:
> On Tuesday, 24 May 2016 at 06:14:49 UTC, Vadim Lopatin wrote:
>> On Thursday, 19 May 2016 at 11:02:00 UTC, pineapple wrote:
>>> I've at least got my code running in windbg on Windows, but I'd also like to get a debugging environment set up in OSX. It looks as though gdb is probably my best option but I haven't been able work out how to get it to work with my compiled D programs.
>>
>> Did someone try to use LLDBMI2 debugger?
>>
>> https://github.com/freedib/lldbmi2
>>
>> It seems to be GDB/MI compatible frontend for LLDB debugger.
>>
>> Should work with Eclipse/DDT
>
> I have seen that there seam to be a problem with the debug source line info that confuses gdb when compiled with dmd. I have filed a bug about this in bugzilla.
> Until this problem is solved, you might have a better chance with gdb when using ldc.

Trying to get DlangIDE + lldbmi2 working.
Partially done (implemented some fixes to support it).
Experimenting with DMD generated program.
Breakpoint setting is working. I can run program, it stops ok on breakpoint (at requested position). Stack frames are shown w/o source file and line number.
Variables are not shown.

Probably, something in DMD debug info is incompatible with LLDB
(or lldbmi2 frontend has some bug)

On Tuesday, 7 June 2016 at 18:35:15 UTC, Vadim Lopatin wrote:
> Trying to get DlangIDE + lldbmi2 working.
> Partially done (implemented some fixes to support it).
> Experimenting with DMD generated program.
> Breakpoint setting is working. I can run program, it stops ok on breakpoint (at requested position). Stack frames are shown w/o source file and line number.
> Variables are not shown.
>
> Probably, something in DMD debug info is incompatible with LLDB
> (or lldbmi2 frontend has some bug)

Managed to hack lldbmi2 to get line numbers working.
But it looks like there are some problems with Function debug information.