Debugger in VS2015 goes nuts!

Elements Oxygene
,
1

Hello,

What I currently notice is, I am not possible to debug this line of code:

 class method Main(args: array of String): Int32;
begin
  const count = 1000;
  var numbers : array[1..count] of Int32; 
  var rnd := new Random(10);
  
  //Das Array mit zufälligen Zahlen füttern
  for x: Int32 := 0 to length(numbers) do
    numbers[x] := rnd.Random();

  writeLn('Pls enter a number..');
  var search: int32 := StrToInt(Console.ReadLine());
  
  writeLn(length(numbers));

  for x in numbers do
    if x = search then
      writeLn('found!');
  
  readLn;
end;

When I set a breakpoint, and the debugger jumps to that BP(breakpoint), I cant continue with F10 so when I try to, it doesnt continue in the code, but lt brings me back to the console instead of continue the lines in the source-code :confused:

OR when I set a BP to this line

image.png1680×1050 117 KB

the debugger doesnt work properly, instead he laggs in that way, that the variable “x” is not getting updated and is even false initialized :confused:

I hope I explained it a little bit, but the debugger goes nuts.

–Shpend

2

Island, i presume? what target platform?

3

Windows 10 x64.

The whole PC is an AMD based PC.

4

Thanks, logged as bugs://78153

5

Thanx. i assume this is with latest beta, not with 9.1 RTM, correct? (the beta has our new Windows debug engine for Island)

6

Yes, it happens with the 9.2.0.2169 Version!

1 Like
7

bugs://78153 got closed with status fixed.

8

Oke so there were a few issues. VS.NET didn’t use the new debug engine (rewritten from scratch by myself, works a lot better imo). there was also a bug in the random class, which gave weird not so random results, fixed that too.

Now the new debug enigne might have a few new bugs that we didn’t have before, but overall should be a LOT better (and it’s the same engine as used in Water with Island).

1 Like