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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.224.20.133 with SMTP id f5mr6109295qab.8.1392483521962; Sat, 15 Feb 2014 08:58:41 -0800 (PST) X-Received: by 10.182.119.133 with SMTP id ku5mr134199obb.4.1392483521845; Sat, 15 Feb 2014 08:58:41 -0800 (PST) Path: border2.nntp.dca.giganews.com!nntp.giganews.com!news-in-01.newsfeed.easynews.com!easynews.com!easynews!news.glorb.com!f11no21059814qae.1!news-out.google.com!h8ni14igy.0!nntp.google.com!c10no23691243igq.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 15 Feb 2014 08:58:41 -0800 (PST) In-Reply-To: <8eouf9logko4l4ee6806hlufrjosbl9h3s@4ax.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=68.4.154.23; posting-account=KSa2aQoAAACOxnC0usBJYX8NE3x3a1Xq NNTP-Posting-Host: 68.4.154.23 References: <87ha81u9r7.fsf@adaheads.sparre-andersen.dk> <3kdtf9l42gimm37vgia3eibsmr638r27ig@4ax.com> <8eouf9logko4l4ee6806hlufrjosbl9h3s@4ax.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <6b15a672-d9af-4580-88b9-435b90789d47@googlegroups.com> Subject: Re: confusing string error From: adambeneschan@gmail.com Injection-Date: Sat, 15 Feb 2014 16:58:41 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 2786 Xref: number.nntp.dca.giganews.com comp.lang.ada:184879 Date: 2014-02-15T08:58:41-08:00 List-Id: On Saturday, February 15, 2014 4:53:42 AM UTC-8, ag...@drrob1.com wrote: > On Sat, 15 Feb 2014 09:33:25 +0000, Simon Wright wrote: > I guess this is a case of the error code does not match the error. I > kept getting an error message about the character appending line. >=20 > I tried GDB and stepped through, and seemed to get the same error. Sometimes the Put_Line debugger does a better job than other debuggers. > I still don't understand why stepping line by line did not show me the > correct failure point. I don't have a way to tell. (I found out what line it was because I tried = it using Irvine Compiler's debugger, which did tell me what the correct lin= e was.) There are some possible reasons that I can think of why incorrect = lines might show up (based on my general experience, not on any particular = knowledge of GNAT/GDB). The source files could just be out of sync; e.g. y= ou edited a file to add some comments but didn't recompile it, or you linke= d using an object file from the wrong place. If your source was in one lar= ge file, and GNATCHOP was called on to split it up, the line may refer to t= he larger file rather than the split-up one or vice versa. Finally, optimi= zation can cause problems when the compiler rearranges code; it can be very= difficult to get it to display correct line numbers. Plus we can't rule o= ut a compiler bug. -- Adam