Re: GDB w/GNAT 3.11p w/NT4.0 Question

[mcc@entropy.cs.princeton.edu (Martin C. Carlisle)]

I have not experienced this problem, but I suggest the following to
narrow it down:

1) Reinstall and see if it goes away.  (Unfortunately, this happens 
far too often on Windows).

2) run GDB from a DOS prompt (gdb myprogram.exe)
and see if it exhibits the same behavior.  

If so, then you've isolated the problem to be outside the editor.  The
GNAT chat list may be a good source of expert advice.  Email 
chat-request@gnat.com to join.

If not, then I suppose it becomes my problem.  Email me at carlislem@acm.org
Please include a copy of the smallest program that behaves poorly.

--Martin

In article <36E81651.5B91E3D3@netspace.net.au>,
Jackie & Barry Schiff  <schiff@netspace.net.au> wrote:
>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.


-- 
Martin C. Carlisle, Asst Prof of Computer Science, US Air Force Academy
mcc@cs.usafa.af.mil, http://www.usafa.af.mil/dfcs/bios/carlisle.html
DISCLAIMER:  This content in no way reflects the opinions, standards or 
policy of the US Air Force Academy or the United States Government.