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,39771fafaed6ec26 X-Google-Attributes: gid103376,public From: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: Gdb gets confused Date: 1996/06/22 Message-ID: #1/1 X-Deja-AN: 162237339 references: organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada Date: 1996-06-22T00:00:00+00:00 List-Id: "We have been using the Ada aware version of GDB (version 4.15.1.gnat.1.10) which usually works great, except that sometimes when it hits a break it gets confused about what function it is in. It correctly identifies the line number and file of the break, but it thinks that it is in a different function from the same file. When it does this it is a pain. We can't see the local variables or arguments, and it can't even step correctly." Incidentally, when you report this to report@gnat.com, you must send along an example, and the chances of the problem being looked at increase inversely with the size of the example you can find that shows the problem. Be sure to say what version of the system you are using. In general, the way we work at ACT is that for our supported customers, we deal with their big programs and real applications if necessary to track down problems (though even there of course it always helps if things can be narrowed down). For unsupported users of GNAT and related tools, we accept bug reports at report@gnat.com and eventually process them, but at low priority. In practice, such reports have a much better chance of being looked at some time soon if they are narrowed down to small examples. A vague report with no details (such as the one above), or a giant program with a note saying simply "this doesn't work, please fix it", is unlikely to get looked at any time soon! Robert Dewar ACT