From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: GPS DEbug problem with Unbounded_String Date: Mon, 07 Jan 2019 15:08:12 +0000 Organization: A noiseless patient Spider Message-ID: References: <5c333543$0$31549$e4fe514c@news.kpn.nl> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader01.eternal-september.org; posting-host="f9b393085badc3d75d1463f1da12d22a"; logging-data="17641"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/6gNUHgabbHYNJPRhJ0+oUamhQI5uS5YQ=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (darwin) Cancel-Lock: sha1:EOz0116ckclhhThPOVACwlGWzQw= sha1:B6D7XDr8W7F8ftEEHOLNd5UCN1I= Xref: reader01.eternal-september.org comp.lang.ada:55238 Date: 2019-01-07T15:08:12+00:00 List-Id: "ldries46" 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.