http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245
--- Comment #7 from Timo Lindfors <timo.lindfors at iki dot fi> 2011-09-08 08:06:42 UTC --- Great news! I can verify that this indeed was fixed in debian (amd64 unstable) too: $ gnatmake -ggdb3 -O0 gdb_bug_2 gcc-4.6 -c -ggdb3 -O0 gdb_bug_2.adb gdb_bug_2.adb:25:07: warning: variable "gs" is read but never assigned gnatbind -x gdb_bug_2.ali gnatlink gdb_bug_2.ali -ggdb3 -O0 (sid)lindi1:~/tmp$ gdb ./gdb_bug_2 GNU gdb (GDB) 7.3-debian Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /home/lindi/tmp/gdb_bug_2...done. (gdb) break breakpoint Breakpoint 1 at 0x401295: file gdb_bug_2.adb, line 15. (gdb) run Starting program: /home/lindi/tmp/gdb_bug_2 Breakpoint 1, gdb_bug_2.fitg5.breakpoint () at gdb_bug_2.adb:15 15 null; (gdb) print var1 $1 = 42 (gdb) print var2 $2 = 43 (gdb) quit A debugging session is active. Inferior 1 [process 12502] will be killed. Quit anyway? (y or n) y (sid)lindi1:~/tmp$ dpkg-query -W gnat-4.6 gnat-4.6 4.6.1-5