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: 162237337 references: organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada Date: 1996-06-22T00:00:00+00:00 List-Id: Michael said "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." What optimization level are you using? Code merging and inlining in higher optimization levels can sometimes cause this. Some standard debugging formats are simply not expressive enough to represent the effects of such optimizations. If you are seeing this in -O0 mode, it certainly represents a bug. I assume you have reported this to report@gnat.com? The folks at ACT who know about GDB don't read CLA!