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.5 required=5.0 tests=BAYES_00,STOX_REPLY_TYPE autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,27544cb48c942326 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.16.35 with SMTP id c3mr1054412pbd.6.1319771656818; Thu, 27 Oct 2011 20:14:16 -0700 (PDT) Path: p6ni8473pbn.0!nntp.google.com!news2.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx01.iad01.newshosting.com!newshosting.com!news2.euro.net!feeder.news-service.com!tudelft.nl!txtfeed1.tudelft.nl!feed.xsnews.nl!border-3.ams.xsnews.nl!upload-2.xsnews.nl!10.10.69.5.MISMATCH!frontend-F09-05.ams.news.kpn.nl From: "ldries46" Newsgroups: comp.lang.ada References: <4ea68441$0$8041$703f8584@textnews.kpn.nl> In-Reply-To: Subject: Re: Length of unbounded_string. Date: Fri, 28 Oct 2011 05:12:54 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 15.4.3538.513 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513 Message-ID: <4eaa1e0b$0$3313$703f8584@news.kpn.nl> Organization: KPN.com NNTP-Posting-Host: 77.168.179.107 X-Trace: 1319771659 news.kpn.nl 3313 77.168.179.107@kpn/77.168.179.107:64218 Xref: news2.google.com comp.lang.ada:14216 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 7bit Date: 2011-10-28T05:12:54+02:00 List-Id: Normally I just write a short test case to try to reproduce the error, but in some cases the error can only be reproduced in a rather complicated situation. In this case the problem is found in such a complicated situation. In the Debugging session there seems to be a discrepancy between the output of the debug command and the print command. The debug command seems to give the same output as the program itself but the print command presents the expected output. This kind of problem is in general no reproducible in a simple program. The problem with a small reproducible test case is just that the small version I wrote did not created the problem. So my question was more do I forget something or do I do something wrong or is there anything wrong somewhere in the "windows version" compiler or the "windows version" of the some of the packages "Brian Drummond" schreef in bericht news:j8bdtm$1hk$2@dont-email.me... On Thu, 27 Oct 2011 09:56:50 +0100, Simon Wright wrote: > "Randy Brukardt" writes: > >> Even people who should know better do it (and I know I have, too). It's >> a pain to create a reproducing example, but a lot of time when I do >> that, it becomes clear what is wrong (and it often is "operator >> error"!). > > Me too. +1. Though the other side is: making the reproducible test case can be significant work in itself,. By the time you have five of them open against a tool (all real bugs : clearly not written in Ada!) you begin to wish you could charge the helpdesk for your time... it's easier than justifying charging it to the project. - Brian