Thread overview |
---|
November 19, 2018 generate debug file, DUB, LDC etc... | ||||
---|---|---|---|---|
| ||||
Im trying to get MSVC to debug my binary. I've added... "dflags": ["-g"], at the top level in dub.json to try and get LDC to generate debug info. But doesnt seem to have done anything. |
November 19, 2018 Re: generate debug file, DUB, LDC etc... | ||||
---|---|---|---|---|
| ||||
Posted in reply to willo | On Monday, 19 November 2018 at 10:04:25 UTC, willo wrote:
> Im trying to get MSVC to debug my binary. I've added...
>
> "dflags": ["-g"],
>
> at the top level in dub.json to try and get LDC to generate debug info. But doesnt seem to have done anything.
I guess you need `-g` for the `lflags` too, assuming dub uses LDC for linking.
|
November 20, 2018 Re: generate debug file, DUB, LDC etc... | ||||
---|---|---|---|---|
| ||||
Posted in reply to kinke | On Monday, 19 November 2018 at 19:52:31 UTC, kinke wrote:
> On Monday, 19 November 2018 at 10:04:25 UTC, willo wrote:
>> Im trying to get MSVC to debug my binary. I've added...
>>
>> "dflags": ["-g"],
>>
>> at the top level in dub.json to try and get LDC to generate debug info. But doesnt seem to have done anything.
>
> I guess you need `-g` for the `lflags` too, assuming dub uses LDC for linking.
My bad, I didn't read the output properly, the debugger couldn't find the debug info for all the system dlls but had found it for my program. There's a box you tick in MSVC options to get it to download debug info for the system dlls, worked ok after that. That said it doesn't work very well.
|
Copyright © 1999-2021 by the D Language Foundation