[Bug ada/37245] GDB reports "No definition of "var1" in current context." for an existing variable

2011-09-08 Thread timo.lindfors at iki dot fi 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245

--- Comment #7 from Timo Lindfors  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 
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:
...
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.64.6.1-5

[Bug ada/37245] GDB reports "No definition of "var1" in current context." for an existing variable

2011-08-31 Thread charlet at gcc dot gnu.org 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245

Arnaud Charlet  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||charlet at gcc dot gnu.org
 Resolution||FIXED
   Target Milestone|--- |4.6.1
  Known to fail||

--- Comment #6 from Arnaud Charlet  2011-09-01 
06:33:31 UTC ---
Closing then, thanks for checking

[Bug ada/37245] GDB reports "No definition of "var1" in current context." for an existing variable

2011-08-31 Thread nicolas.boulenguez at free dot fr 
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 results so far:
4.1.2 reports 1
4.1.3 ok
4.2.3 ok
4.3.1 no definition
4.4.6 no definition
4.6.1 ok

[Bug ada/37245] GDB reports "No definition of "var1" in current context." for an existing variable

2011-08-31 Thread timo.lindfors at iki dot fi 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245

--- Comment #4 from Timo Lindfors  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: warning: variable "gs" is read but never assigned
gnatbind -x gdb_bug_2.ali
gnatlink gdb_bug_2.ali -ggdb3
lindi2:~/tmp$ gdb ./gdb_bug_2
GNU gdb (GDB) 7.2-debian
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
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:
...
Reading symbols from /home/lindi/tmp/gdb_bug_2...done.
(gdb) break breakpoint
Breakpoint 1 at 0x401322: file gdb_bug_2.adb, line 16.
(gdb) run
Starting program: /home/lindi/tmp/gdb_bug_2 

Breakpoint 1, gdb_bug_2.fitg5.breakpoint () at gdb_bug_2.adb:16
16  end Breakpoint;
(gdb) print var1
No definition of "var1" in current context.
(gdb) print var2
$1 = 43
(gdb) quit
A debugging session is active.

Inferior 1 [process 11766] will be killed.

Quit anyway? (y or n) y
lindi2:~/tmp$ dpkg-query -W gdb
gdb7.2-1
lindi2:~/tmp$ dpkg-query -W gcc
gcc4:4.6.1-2
lindi2:~/tmp$ cat /proc/version 
Linux version 3.0.0-1-amd64 (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version
4.5.3 (Debian 4.5.3-4) ) #1 SMP Sun Jul 24 02:24:44 UTC 2011
lindi2:~/tmp$ md5sum gdb_bug_2.adb 
58638c361f25465b7a6288d0a69c7964  gdb_bug_2.adb


and unstable:


(sid)lindi1:~/tmp$ gnatmake -ggdb3 -O0 gdb_bug_2
gcc-4.4 -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
(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 
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:
...
Reading symbols from /home/lindi/tmp/gdb_bug_2...done.
(gdb) break breakpoint
Breakpoint 1 at 0x401322: file gdb_bug_2.adb, line 16.
(gdb) run
Starting program: /home/lindi/tmp/gdb_bug_2 

Breakpoint 1, gdb_bug_2.fitg5.breakpoint () at gdb_bug_2.adb:16
16  end Breakpoint;
(gdb) print var1
No definition of "var1" in current context.
(gdb) print var2
$1 = 43
(gdb) quit
A debugging session is active.

Inferior 1 [process 16208] will be killed.

Quit anyway? (y or n) y
(sid)lindi1:~/tmp$ dpkg-query -W gdb
gdb7.3-1
(sid)lindi1:~/tmp$ dpkg-query -W gcc
gcc4:4.6.1-2
(sid)lindi1:~/tmp$ cat /proc/version 
Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) (da...@debian.org) (gcc version
4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:42:28 UTC 2011

(the unstable one is in a chroot so it is running older kernel in case you
wonder.)

[Bug ada/37245] GDB reports "No definition of "var1" in current context." for an existing variable

2011-08-31 Thread nicolas.boulenguez at free dot fr 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245

nicolas.boulenguez at free dot fr changed:

   What|Removed |Added

 CC||nicolas.boulenguez at free
   ||dot fr

--- Comment #3 from nicolas.boulenguez at free dot fr 2011-08-31 23:59:48 UTC 
---
Linux 3.0.0-1-amd64 x86_64 gcc 4.6.1 (-5 in debian) and gdb 7.2 (-debian)
gdb reports the correct answer $1 = 42

[Bug ada/37245] GDB reports "No definition of "var1" in current context." for an existing variable

2008-08-26 Thread ludovic at ludovic-brenta dot org 


--- 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

  Known to fail||4.1.2 4.3.1 4.4.0
  Known to work||4.2.3


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245

[Bug ada/37245] GDB reports "No definition of "var1" in current context." for an existing variable

2008-08-26 Thread ludovic at ludovic-brenta dot org 


--- 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=16151&action=view)
Source file that reproduces the problem


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37245