Thread overview
VisualD: Errors do not break on line they occur
Apr 18, 2017
Mike B Johnson
Apr 19, 2017
Mike B Johnson
Apr 19, 2017
Mike B Johnson
Apr 19, 2017
Rainer Schuetze
April 18, 2017
e.g., I get a range error when calling a method and it breaks at the method call rather than inside the method. The reported line where the error occurred is correct though. Requires me to go hunt down the line though.
April 19, 2017
On Tuesday, 18 April 2017 at 22:34:38 UTC, Mike B Johnson wrote:
> e.g., I get a range error when calling a method and it breaks at the method call rather than inside the method. The reported line where the error occurred is correct though. Requires me to go hunt down the line though.

Also, it seems that when using regex functions(match) and trying to step over source code, one gets a "source not found" type of error and the debugger ends up stepping over everything rather than returning right back to the next line.

e.g.,

foreach(a; match())
{
 // stepping over the foreach will never allow reaching this code or any code below it unless a BP exists. normal code will enter the foreach.
}

April 19, 2017
A similar issue I am having is that some breakpoints can't be hit(whited out BP).

Visual studio says the BP has no symbols but I think this is an error. I have gotten the BP to work on the line at times by removing it and adding it back in or setting another BP then setting it. (rarely works but I've seen it happen)


April 19, 2017

On 19.04.2017 03:51, Mike B Johnson wrote:
> A similar issue I am having is that some breakpoints can't be hit(whited
> out BP).

Line information emitted by the compiler (I guess you are using dmd) is sometimes a bit off. Reproducible examples would be nice. You can also report them at issues.dlang.org.


>
> Visual studio says the BP has no symbols but I think this is an error. I
> have gotten the BP to work on the line at times by removing it and
> adding it back in or setting another BP then setting it. (rarely works
> but I've seen it happen)
>

Not sure about this, sounds like a debugger issue. Reproducible example code?