August 03, 2017 Re: Visual D no bp's on x64 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Rainer Schuetze | On Thursday, 3 August 2017 at 07:06:06 UTC, Rainer Schuetze wrote:
>
>
> On 31.07.2017 19:51, Johnson Jones wrote:
>> On Saturday, 22 July 2017 at 12:54:17 UTC, Rainer Schuetze wrote:
>>>
>>>
>>> On 18.06.2017 20:25, Mike B Johnson wrote:
>>>> [...]
>>>
>>> After installing VS2017 on a fresh Win10 install I could reproduce this issue: the mago debug engine failed to load the symbols when only VS2017 is installed, because the COM-CLSID to load msdia140.dll changed. Switching to the VS debug engine worked, though.
>>>
>>> Should be fixed in the next release.
>>
>> I installed a fresh VS2017 and the latest beta visual D and same issues. As of today, was this suppose to be fixed?
>
> It hasn't been released until now: https://github.com/dlang/visuald/releases/tag/v0.45.0
Thanks! Seems to be working.
|
August 06, 2017 Re: Visual D no bp's on x64 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Johnson Jones | On Thursday, 3 August 2017 at 20:22:56 UTC, Johnson Jones wrote:
> On Thursday, 3 August 2017 at 07:06:06 UTC, Rainer Schuetze wrote:
>>
>>
>> On 31.07.2017 19:51, Johnson Jones wrote:
>>> On Saturday, 22 July 2017 at 12:54:17 UTC, Rainer Schuetze wrote:
>>>>
>>>>
>>>> On 18.06.2017 20:25, Mike B Johnson wrote:
>>>>> [...]
>>>>
>>>> After installing VS2017 on a fresh Win10 install I could reproduce this issue: the mago debug engine failed to load the symbols when only VS2017 is installed, because the COM-CLSID to load msdia140.dll changed. Switching to the VS debug engine worked, though.
>>>>
>>>> Should be fixed in the next release.
>>>
>>> I installed a fresh VS2017 and the latest beta visual D and same issues. As of today, was this suppose to be fixed?
>>
>> It hasn't been released until now: https://github.com/dlang/visuald/releases/tag/v0.45.0
>
> Thanks! Seems to be working.
well, in x86 I still get a few BP's that won't be hit every once in a while(well, happened for the first time since I've used the new release).
The code looks like
while(i < data.length && data[i] != '>' && data[i] != '"' && data[i..i+token2.length] != token2) i++;
if (data[i] == '>') { continue; }
I put a BP on the if and when ran it says it won't be hit. I have a BP right above it and below it and it works fine.
says "The BP will not currently be hit. No symbols have been loaded for this document.". I do not know why symbols really matter for BP's?
If I change the if statement to
if (data[i] == '>')
{
continue;
}
it works ;/
|
August 06, 2017 Re: Visual D no bp's on x64 | ||||
---|---|---|---|---|
| ||||
Posted in reply to FoxyBrown | On Sunday, 6 August 2017 at 03:12:22 UTC, FoxyBrown wrote:
> On Thursday, 3 August 2017 at 20:22:56 UTC, Johnson Jones wrote:
>> On Thursday, 3 August 2017 at 07:06:06 UTC, Rainer Schuetze wrote:
>>> [...]
>>
>> Thanks! Seems to be working.
>
> well, in x86 I still get a few BP's that won't be hit every once in a while(well, happened for the first time since I've used the new release).
>
>
> The code looks like
>
> while(i < data.length && data[i] != '>' && data[i] != '"' && data[i..i+token2.length] != token2) i++;
> if (data[i] == '>') { continue; }
>
> I put a BP on the if and when ran it says it won't be hit. I have a BP right above it and below it and it works fine.
>
> says "The BP will not currently be hit. No symbols have been loaded for this document.". I do not know why symbols really matter for BP's?
>
>
> If I change the if statement to
>
> if (data[i] == '>')
> {
> continue;
> }
>
> it works ;/
Oops, it "works". The BP icon is no longer a hollow read disk but it is simply not hit ;/
I know all this doesn't help much but it all seems to be related to the previous bugs.
|
August 06, 2017 Re: Visual D no bp's on x64 | ||||
---|---|---|---|---|
| ||||
Posted in reply to FoxyBrown |
On 06.08.2017 05:21, FoxyBrown wrote:
> On Sunday, 6 August 2017 at 03:12:22 UTC, FoxyBrown wrote:
>> On Thursday, 3 August 2017 at 20:22:56 UTC, Johnson Jones wrote:
>>> On Thursday, 3 August 2017 at 07:06:06 UTC, Rainer Schuetze wrote:
>>>> [...]
>>>
>>> Thanks! Seems to be working.
>>
>> well, in x86 I still get a few BP's that won't be hit every once in a while(well, happened for the first time since I've used the new release).
>>
>>
>> The code looks like
>>
>> while(i < data.length && data[i] != '>' && data[i] != '"' && data[i..i+token2.length] != token2) i++;
>> if (data[i] == '>') { continue; }
>>
>> I put a BP on the if and when ran it says it won't be hit. I have a BP right above it and below it and it works fine.
>>
>> says "The BP will not currently be hit. No symbols have been loaded for this document.". I do not know why symbols really matter for BP's?
>>
>>
>> If I change the if statement to
>>
>> if (data[i] == '>')
>> {
>> continue;
>> }
>>
>> it works ;/
>
> Oops, it "works". The BP icon is no longer a hollow read disk but it is simply not hit ;/
>
> I know all this doesn't help much but it all seems to be related to the previous bugs.
It would be good if you could post the full function, even better a complete compilable file exposing the problem.
I suspect dmd just doesn't produce proper debug information. For example "continue" is often optimized away due to some branches even removed in debug code.
|
Copyright © 1999-2021 by the D Language Foundation