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,8e043bdbf6c695f7 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: GDB with GNAT 3.04 for DOS Date: 1996/12/23 Message-ID: #1/1 X-Deja-AN: 205604908 references: <1996Dec23.122040.5430@news> organization: New York University newsgroups: comp.lang.ada Date: 1996-12-23T00:00:00+00:00 List-Id: Rich Maggio writes: >... > I was able to get around the debugger except for one case. I found that I > could not step into code that existed in a generic package. The debugger > seemed to go off into nowhere land - referencing random lines of code in my > source. It did not generate any error messages or anything. That's odd, but might be a result of using an old version of GNAT. Certainly I step into generic code all the time, and in fact you can successfully set breakpoints in generic code as well (i.e. in a specific instance) by using the properly qualified name of the subprogram. My suggestion is to try this again with 3.07 when it is available, and then if you have a specific instance of failure, report it with as much detail as possible to report@gnat.com. Robert Dewar Ada Core Technologies