New Lazuras IDE

[JLWest]

Code: Pascal  [Select][+][-]

1.  procedure TForm1.FormCreate(Sender: TObject);
2.   var valid : boolean;
3.       Loc : String = '';
4.       FileName :String;
5.   begin
6.    Loc := ProgramDirectory;
7.    FileName := Loc + 'apt.txt';
8.    valid := fileexists(C_AptDotDat);
9.    ListBox1.Clear;
10.    ListBox1a.Clear;
11.    ListBox2.Clear;
12.    ListBox3.Clear;
13.    ListBox4.Clear;
14.    ListBox5.Clear;
15.    ListBox6.Clear;
16.    LoadAllListBoxes;
17.    ListBox7.Clear;
18.   end;                    

This is what Line 6 returns.
'X:\A Current Project\Mast###(gdb unparsed remainder:...)###'
This started after I installed Lazuras ver 2.0.2

[RAW]

??? Are you searching for Application.Location ???

[JLWest]

Yes and under the debugger it returns the following:

'X:\A Current Project\Mast###(gdb unparsed remainder:...)###'

with all the trash after X:\A Current Project\Mast i.e ###(gdb unparsed remainder:...)###

[RAW]

No problem here ... 

Edit: OK, I see it now ... LOCAL VARIABLES
Did you check if there is already a bug report?

by the way: use WATCHES instead ... 

[Martin_fr]

GDB believes the string is an array.
Therefore the following setting applies (Tools > Option > Debugger > [property grid]: MaxLocalsLengthForStaticArray

This setting is 25 by default, because normally the "Locals" window, is hardly ever big enough to even show more than 10 elements.

I wasn't aware that this affects strings. So maybe the default needs to increase.
But that then opens up another issue (for which this was meant to be a fix):
  Array[0..10000] of TBigRecord;
Will print n elements of TBigRecord => which can be seriously slow. And the local window has no option to exclude any local var.
This also affects the Stack window.
And both are evaluated even if closed, which means people may have to wait serious time before they can continue stepping.

Whats the typical width of your Locals windows?
Mine would typically be width enough to show the first 80 to 90 chars. So setting the default to 100 should cover most cases.

I know 100 is still very small for strings, but can already lead to very serious slow downs.
Ideally the local window needs some interactive feature, allowing to fetch the remainder.

[JLWest]

@Martin_fr

Is this something new in 2.0.2. I didn't have this in the previous IDE.

Is there a way to go back to the previous version of the IDE?
I just downloaded the2.0.2 and started using it. Should I be doing something more. Configuration or setup or something?

I'll change the setting and  see if that helps.

Thanks for your help.

[Martin_fr]

Not sure in which version exactly it was added:

But this can be configured: Tools > Option > Debugger > [property grid]: MaxLocalsLengthForStaticArray

Default is 25. You can set it to as high as you want.

[jamie]

why not use the already provided string for this purpose ?

Application.Location

[Martin_fr]

Just note: The value shown by the debugger, is "cut off" (and appended "gdb unparsed ...")

The real value is different.
The setting I mentioned will enable the debugger to show the actual value.

[JLWest]

I got this same issue again.  '\Mast###(gdb unparsed remainder:...)###'

I had made the change in setting:
Tools >Options>Debugger>General>MaxLocalLengthForLocalArray = 80

and the issue went away for a while.

So I went back to: Tools >Options>Debugger>General>MaxLocalLengthForLocalArray = 25
and it was set to 25?

I didn't change it, download a new IDE or even go back into Tools.

So I changed it back to 80 and the issue went away.

Seems to me to be a Bug or maybe it a new feature say 'Soft configuration'.

[Martin_fr]

I observed that with other settings, that got lost.... But I was never able to reproduce it. Which means I have no way to fix it.

My assumption is/was (but again, I was not able to reproduce) that it may happen if you change the "debugger type"
Did you try any other debugger type? (eg gdb server, or fpdebug?)

[JLWest]

No I sisn't try any other debugger type.