Hi everyone,

Just wrote annotated v1.2.7 of Mono-D:
http://mono-d.alexanderbothe.com/completion-ldc2-compatibility-dub-fix-v1-2-7

I'm too lazy to mention every part of it again over here - if there are questions: Here, in #d.mono-d, on the blog, on github - you know the usual places where to find me :)



Cheers mates,
Alex

On Sunday, 12 January 2014 at 23:40:33 UTC, Alexander Bothe wrote:
> Hi everyone,
>
> Just wrote annotated v1.2.7 of Mono-D:
> http://mono-d.alexanderbothe.com/completion-ldc2-compatibility-dub-fix-v1-2-7
>
> I'm too lazy to mention every part of it again over here - if there are questions: Here, in #d.mono-d, on the blog, on github - you know the usual places where to find me :)
>
>
>
> Cheers mates,
> Alex

after about half year i tried it again on OS X, and Mono-D is
quite good for  writing the code, but... the debug!!11

can we haz some GDB or LLDB(or both :)) support please? it
shouldn't be that hard porting linux code to OS X. it may already
doing something useful but it simply doesn't start...

p.s. also, why at first launch it can't just fetch default phobos
location for DMD? it's quite annoying adding this paths in
settings and it may revolve unaware users from using it(like it
was for me about year ago).

On Monday, 13 January 2014 at 05:25:31 UTC, evilrat wrote:
> On Sunday, 12 January 2014 at 23:40:33 UTC, Alexander Bothe wrote:
>> Hi everyone,
>>
>> Just wrote annotated v1.2.7 of Mono-D:
>> http://mono-d.alexanderbothe.com/completion-ldc2-compatibility-dub-fix-v1-2-7
>>
>> I'm too lazy to mention every part of it again over here - if there are questions: Here, in #d.mono-d, on the blog, on github - you know the usual places where to find me :)
>>
>>
>>
>> Cheers mates,
>> Alex
>
> after about half year i tried it again on OS X, and Mono-D is
> quite good for  writing the code, but... the debug!!11
>
> can we haz some GDB or LLDB(or both :)) support please? it
> shouldn't be that hard porting linux code to OS X. it may already
> doing something useful but it simply doesn't start...
>
> p.s. also, why at first launch it can't just fetch default phobos
> location for DMD? it's quite annoying adding this paths in
> settings and it may revolve unaware users from using it(like it
> was for me about year ago).

It happened to me yesterday as well after the update.

Is this some regression? It worked out of the box previously.

--
Paulo

On Monday, 13 January 2014 at 05:25:31 UTC, evilrat wrote:
> after about half year i tried it again on OS X, and Mono-D is
> quite good for  writing the code, but... the debug!!11
>
> can we haz some GDB or LLDB(or both :)) support please? it
> shouldn't be that hard porting linux code to OS X. it may already
> doing something useful but it simply doesn't start...

I've got no OSX but erm, what tool is required to have lldb information generated? ldc2?
On the other side, which tool is then required to get gdb debug info?

> p.s. also, why at first launch it can't just fetch default phobos
> location for DMD? it's quite annoying adding this paths in
> settings and it may revolve unaware users from using it(like it
> was for me about year ago).

Despite it's clearly explained in the set up guide it sounds quite reasonable to do this automatically, you're right.

On Monday, 13 January 2014 at 11:03:45 UTC, Alexander Bothe wrote:
> On Monday, 13 January 2014 at 05:25:31 UTC, evilrat wrote:
>> after about half year i tried it again on OS X, and Mono-D is
>> quite good for  writing the code, but... the debug!!11
>>
>> can we haz some GDB or LLDB(or both :)) support please? it
>> shouldn't be that hard porting linux code to OS X. it may already
>> doing something useful but it simply doesn't start...
>
> I've got no OSX but erm, what tool is required to have lldb information generated? ldc2?
> On the other side, which tool is then required to get gdb debug info?

i don't know about other tools, so basically i just build with "dmd files.d -gc" and debug using console lldb, of course it was mangled but it is better than nothing.

On 2014-01-13 12:03, Alexander Bothe wrote:

> I've got no OSX but erm, what tool is required to have lldb information
> generated? ldc2?
> On the other side, which tool is then required to get gdb debug info?

With DMD I get the line numbers in a backtrace, both in gdb and lldb. I compiled with -g. You won't get any demangling with lldb or gdb supplied by Apple.

-- 
/Jacob Carlborg

On Monday, 13 January 2014 at 11:49:57 UTC, evilrat wrote:
> On Monday, 13 January 2014 at 11:03:45 UTC, Alexander Bothe wrote:
>> On Monday, 13 January 2014 at 05:25:31 UTC, evilrat wrote:
>>> after about half year i tried it again on OS X, and Mono-D is
>>> quite good for  writing the code, but... the debug!!11
>>>
>>> can we haz some GDB or LLDB(or both :)) support please? it
>>> shouldn't be that hard porting linux code to OS X. it may already
>>> doing something useful but it simply doesn't start...
>>
>> I've got no OSX but erm, what tool is required to have lldb information generated? ldc2?
>> On the other side, which tool is then required to get gdb debug info?
>
> i don't know about other tools, so basically i just build with "dmd files.d -gc" and debug using console lldb, of course it was mangled but it is better than nothing.

Fortunately I implemented demangling already, so that's not a real problem.

So according to Jacob's comment it's actually possible to get gdb on OSX - but probably just with a wrong build configuration, i.e. the mi2 interface for gdb is not available - or is it? Just try executing gdb --interpreter=mi2 to see whether Mono-D is able to handle its output properly.

On Monday, 13 January 2014 at 05:25:31 UTC, evilrat wrote:
> p.s. also, why at first launch it can't just fetch default phobos
> location for DMD? it's quite annoying adding this paths in
> settings and it may revolve unaware users from using it(like it
> was for me about year ago).

Okay, implemented it in v1.3

On Monday, 13 January 2014 at 14:50:05 UTC, Alexander Bothe wrote:
> So according to Jacob's comment it's actually possible to get gdb on OSX - but probably just with a wrong build configuration, i.e. the mi2 interface for gdb is not available - or is it? Just try executing gdb --interpreter=mi2 to see whether Mono-D is able to handle its output properly.

running "gdb --interpreter=mi2" launches it without any warnings and errors.

(my gdb version is 7.6)

On Tuesday, 14 January 2014 at 04:10:03 UTC, evilrat wrote:
> On Monday, 13 January 2014 at 14:50:05 UTC, Alexander Bothe wrote:
>> So according to Jacob's comment it's actually possible to get gdb on OSX - but probably just with a wrong build configuration, i.e. the mi2 interface for gdb is not available - or is it? Just try executing gdb --interpreter=mi2 to see whether Mono-D is able to handle its output properly.
>
> running "gdb --interpreter=mi2" launches it without any warnings and errors.
>
> (my gdb version is 7.6)

but running mono-d debug gives following error message

"ApplicationName='gdb', CommandLine=-quiet -fullname -i=mi2', CurrentDirectory=", NativeError= Cannot find the specified file