Anyone who builds dmd with ldc with visual d. Is there anyway to prevent it from losing debug information? The enum issue is related to dmd poor generation of the debug information where in ldc, the it is working as intended. Yet for some reason I am experiencing the same issue with ldc, and I not sure it due to the debug information being lost when compiling.

-Alex

On Thursday, 25 February 2021 at 04:00:09 UTC, 12345swordy wrote:
> Anyone who builds dmd with ldc with visual d. Is there anyway to prevent it from losing debug information? The enum issue is related to dmd poor generation of the debug information where in ldc, the it is working as intended. Yet for some reason I am experiencing the same issue with ldc, and I not sure it due to the debug information being lost when compiling.
>
> -Alex

With LDC, the enum types are displayed correctly:

https://imgur.com/a/aXeIUjV

On Thursday, 25 February 2021 at 07:07:34 UTC, Rumbu wrote:
> On Thursday, 25 February 2021 at 04:00:09 UTC, 12345swordy wrote:
>> Anyone who builds dmd with ldc with visual d. Is there anyway to prevent it from losing debug information? The enum issue is related to dmd poor generation of the debug information where in ldc, the it is working as intended. Yet for some reason I am experiencing the same issue with ldc, and I not sure it due to the debug information being lost when compiling.
>>
>> -Alex
>
> With LDC, the enum types are displayed correctly:
>
> https://imgur.com/a/aXeIUjV

You misunderstanding what I am trying to say here. When I tried to debug the dmd compiler that is built with ldc by using the visual d solution file. The enum information seemed to gotten loss.

-Alex

On Thursday, 25 February 2021 at 14:38:31 UTC, 12345swordy wrote:
> You misunderstanding what I am trying to say here. When I tried to debug the dmd compiler that is built with ldc by using the visual d solution file. The enum information seemed to gotten loss.

Are you referring to Visual D's /DEBUG:FASTLINK again? Then check the object files instead of the .pdb. Or use build.d to generate a full .pdb.

On Thursday, 25 February 2021 at 15:14:43 UTC, kinke wrote:
> On Thursday, 25 February 2021 at 14:38:31 UTC, 12345swordy wrote:
>> You misunderstanding what I am trying to say here. When I tried to debug the dmd compiler that is built with ldc by using the visual d solution file. The enum information seemed to gotten loss.
>
> Are you referring to Visual D's /DEBUG:FASTLINK again? Then check the object files instead of the .pdb. Or use build.d to generate a full .pdb.

It doesn't generate any objects files, only the .pdb file.

-Alex