Hi,

for a while now I've been getting an error popup from Visual d when I build my project (and build succeeds). I've got no idea why or how it started (perhaps after some dmd update). Building works fine, but the error box is getting pretty annoying.
I'm running latest visual D in VS2013 community.

Anyways, here's the error:

core.exception.RangeError@pipedmd(286): Range violation
---------------

and no additional information... or debug logs.

On Sunday, 17 July 2016 at 21:36:08 UTC, Random D user wrote:
> Hi,
>
> for a while now I've been getting an error popup from Visual d when I build my project (and build succeeds). I've got no idea why or how it started (perhaps after some dmd update). Building works fine, but the error box is getting pretty annoying.
> I'm running latest visual D in VS2013 community.
>
> Anyways, here's the error:
>
> core.exception.RangeError@pipedmd(286): Range violation
> ---------------
>
> and no additional information... or debug logs.


I've had similar problems. Always a range violation. Would be really nice if the code at that point spit out more info. I think the problem is not always due to pipedmd though and it is a red herring error.

On 17.07.2016 23:36, Random D user wrote:
> Hi,
>
> for a while now I've been getting an error popup from Visual d when I
> build my project (and build succeeds). I've got no idea why or how it
> started (perhaps after some dmd update). Building works fine, but the
> error box is getting pretty annoying.
> I'm running latest visual D in VS2013 community.
>
> Anyways, here's the error:
>
> core.exception.RangeError@pipedmd(286): Range violation
> ---------------
>
> and no additional information... or debug logs.

Seems this can happen if an output line is of length 2048. There should have been a warning or error though, but maybe it has been swallowed by the range error. Will be fixed in the next release.

BTW: you can also file issues for Visual D at https://issues.dlang.org/

On Tuesday, 19 July 2016 at 06:01:28 UTC, Rainer Schuetze wrote:
> Will be fixed in the next release.

Thanks.