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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,d423dccf160531eb X-Google-Attributes: gid103376,public From: "Steve Doiel" Subject: Re: GDB w/GNAT 3.11p w/NT4.0 Question Date: 1999/03/12 Message-ID: <36e9d084.0@news.pacifier.com>#1/1 X-Deja-AN: 454419842 References: <36E81651.5B91E3D3@netspace.net.au> <7cb8fc$o2f$1@cnn.Princeton.EDU> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Trace: 12 Mar 1999 18:42:12 PST, 216.65.138.160 Newsgroups: comp.lang.ada Date: 1999-03-12T00:00:00+00:00 List-Id: FYI: I experiece the same behaviour. My answer? I run the debugger from a command line in a console window. SteveD >I am using it under NT 4.0, and so far am using the AdaGIDE editor >>environment installed with it (used to use EMACS and maybe will switch >>again but just giving this a try). Anyhow I have a program with text_io >>input/output. When I go to run it under the debugger, which I do by >>hitting the debug button inside of AdaGIDE, the output seems to get >>correctly redirected to an MSDOS command window but it appears that the >>input does not. Thus the program bombs once it gets to an input >>statement (eg. Text_io.Get_Line). Surely I must be doing something >>wrong I just have not dug it out yet. If anybody knows the answer I >>would surely appreciate it.