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
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245
Arnaud Charlet charlet at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245
nicolas.boulenguez at free dot fr changed:
What|Removed |Added
CC||nicolas.boulenguez at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245
--- Comment #4 from Timo Lindfors timo.lindfors at iki dot fi 2011-09-01
00:31:16 UTC ---
The bug still occurs for me on debian testing:
lindi2:~/tmp$ gnatmake -ggdb3 -O0 gdb_bug_2
gcc-4.4 -c -ggdb3 -O0 gdb_bug_2.adb
gdb_bug_2.adb:25:07:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245
--- Comment #5 from nicolas.boulenguez at free dot fr 2011-09-01 01:15:04 UTC
---
During the Debian transition, the default gnat (4.4.6) uses its own gcc instead
of the default gcc (4.6.1), as you can see in line 2 of your log.
Summary of our
--- Comment #1 from ludovic at ludovic-brenta dot org 2008-08-26 17:43
---
Created an attachment (id=16151)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16151action=view)
Source file that reproduces the problem
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245
--- Comment #2 from ludovic at ludovic-brenta dot org 2008-08-26 17:49
---
Note that 4.1.2 fails in a different way than 4.3.1 and trunk.
--
ludovic at ludovic-brenta dot org changed:
What|Removed |Added
