Thread overview | |||||||
---|---|---|---|---|---|---|---|
|
January 25, 2017 Expression could not be evalulated in Visual D. | ||||
---|---|---|---|---|
| ||||
For virtually all values in the debugger local and watch, I get expression cannot be evaluated. "D0001: Error: Expression couldn't be evaluated" This usually happens when expanding a class. I know this isn't helping much, but it is all I have ;/ |
January 25, 2017 Re: Expression could not be evalulated in Visual D. | ||||
---|---|---|---|---|
| ||||
Posted in reply to Profile Anaysis | On Wednesday, 25 January 2017 at 01:10:31 UTC, Profile Anaysis wrote:
> For virtually all values in the debugger local and watch, I get expression cannot be evaluated.
>
> "D0001: Error: Expression couldn't be evaluated"
>
> This usually happens when expanding a class.
>
> I know this isn't helping much, but it is all I have ;/
When I switch to VS debugger and force "use selected debugger" for cv2pdb I get correct values for local variables at least.
Before I was getting 1 for some pointers and it made no sense, switched the debugger and how they are shown correctly in the watch windows.
There seems to be some funny business in the debugger for mago and VS.
|
January 25, 2017 Re: Expression could not be evalulated in Visual D. | ||||
---|---|---|---|---|
| ||||
Posted in reply to Profile Anaysis | On Wednesday, 25 January 2017 at 01:38:45 UTC, Profile Anaysis wrote:
> On Wednesday, 25 January 2017 at 01:10:31 UTC, Profile Anaysis wrote:
>> For virtually all values in the debugger local and watch, I get expression cannot be evaluated.
>>
>> "D0001: Error: Expression couldn't be evaluated"
>>
>> This usually happens when expanding a class.
>>
>> I know this isn't helping much, but it is all I have ;/
>
> When I switch to VS debugger and force "use selected debugger" for cv2pdb I get correct values for local variables at least.
>
> Before I was getting 1 for some pointers and it made no sense, switched the debugger and how they are shown correctly in the watch windows.
>
> There seems to be some funny business in the debugger for mago and VS.
But in the VS debugger some variables that showed up in mago don't show up. I am not seeing some static variables that I could see in mago. The listing shows a row where it might be but the name and value are blank.
|
January 26, 2017 Re: Expression could not be evalulated in Visual D. | ||||
---|---|---|---|---|
| ||||
Posted in reply to Profile Anaysis | On 25.01.2017 02:10, Profile Anaysis wrote: > For virtually all values in the debugger local and watch, I get > expression cannot be evaluated. > > "D0001: Error: Expression couldn't be evaluated" > > This usually happens when expanding a class. > > I know this isn't helping much, but it is all I have ;/ > > > Maybe you are hit by missing debug information in libraries? See https://issues.dlang.org/show_bug.cgi?id=4014 cv2pdb reconstructs some information for Object. |
January 27, 2017 Re: Expression could not be evalulated in Visual D. | ||||
---|---|---|---|---|
| ||||
Posted in reply to Rainer Schuetze | On Thursday, 26 January 2017 at 07:57:58 UTC, Rainer Schuetze wrote:
>
>
> On 25.01.2017 02:10, Profile Anaysis wrote:
>> For virtually all values in the debugger local and watch, I get
>> expression cannot be evaluated.
>>
>> "D0001: Error: Expression couldn't be evaluated"
>>
>> This usually happens when expanding a class.
>>
>> I know this isn't helping much, but it is all I have ;/
>>
>>
>>
>
> Maybe you are hit by missing debug information in libraries? See https://issues.dlang.org/show_bug.cgi?id=4014
>
> cv2pdb reconstructs some information for Object.
Not sure... Seems if I play around with the settings I can get it to go away but my problem of some symbols not showing still holds.
|
Copyright © 1999-2021 by the D Language Foundation