GPS DEbug problem with Unbounded_String

GPS DEbug problem with Unbounded_String

[ldries46]

I am debugging a program with much Unbounded_String data. I do want to show 
the value of such a String. So i need to see **.reference.data. So far aso 
good that works, but the value I get is sometimes an incomplete string and 
sometimes a string with a lot of hexadecimal values. The last I can 
understand, but the first??? I know that the rest of the value is present 
because I can show the value of the length which is correct or can search 
for a character in the part thast is not presented and that also works, but 
it is annoying that the debugger works that way. Is there a setting of  GPS 
that can correct that behavior? 

Re: GPS DEbug problem with Unbounded_String

[Simon Wright]

"ldries46" <bertus.dries@planet.nl> writes:

> I am debugging a program with much Unbounded_String data. I do want to
> show the value of such a String. So i need to see
> **.reference.data. So far aso good that works, but the value I get is
> sometimes an incomplete string and sometimes a string with a lot of
> hexadecimal values. The last I can understand, but the first??? I know
> that the rest of the value is present because I can show the value of
> the length which is correct or can search for a character in the part
> thast is not presented and that also works, but it is annoying that
> the debugger works that way. Is there a setting of  GPS that can
> correct that behavior? 

https://github.com/AdaCore/gnat-gdb-scripts/ includes gnatdbg/strings.py
which includes unbounded string support. I haven't tried it.