From: Simon Wright <simon@pushface.org>
Subject: Re: GPS DEbug problem with Unbounded_String
Date: Mon, 07 Jan 2019 15:08:12 +0000
Date: 2019-01-07T15:08:12+00:00 [thread overview]
Message-ID: <lyr2do1p5v.fsf@pushface.org> (raw)
In-Reply-To: 5c333543$0$31549$e4fe514c@news.kpn.nl
"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.
prev parent reply other threads:[~2019-01-07 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 11:17 GPS DEbug problem with Unbounded_String ldries46
2019-01-07 15:08 ` Simon Wright [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox