Your message dated Sun, 13 Jul 2014 01:38:55 +0000 with message-id <[email protected]> and subject line Bug#714577: Removed package(s) from unstable has caused the Debian Bug report #58329, regarding [fixed in 4.6] gnat library compiled with bad path to sources to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 58329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=58329 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnat Version: 3.12p-4 When I try to debug a program compiled with gnat, either by calling gdb directly, or with the gnatmem leak checker, I get errors that the debugger can't find the location of any Ada library source files. For example, for this simple "hello, world" program: with Text_IO; use Text_IO; procedure Hello is begin Put_Line("Hello, world!"); end Hello; $ gnatmake -g hello .. compiling .. $ gdb hello GNU gdb 19990928 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... (gdb) break hello.adb:6 Breakpoint 1 at 0x8048f93: file hello.adb, line 6. (gdb) run Starting program: /home/jehamby/Code/hello Breakpoint 1, _ada_hello () at hello.adb:6 6 Put_Line("Hello, world!"); (gdb) step ada__text_io__put_line__2 (item={P_ARRAY = 0x8049eac, P_BOUNDS = 0x8049ebc}) at a-textio.adb:1089 1089 a-textio.adb: No such file or directory. (gdb) A similar error occurs with gnatmem, but that appears to be a different problem which I'll file in a separate bug report: $ gnatmem hello 443 a-except.adb: No such file or directory. ### incorrect user program termination detected. following data may not be meaningful Global information ------------------ Total number of allocations : 0 Total number of deallocations : 0 Final Water Mark (non freed mem) : 0 Bytes High Water Mark : 0 Bytes By running strace, I was able to determine that GDB is looking for the files in /home/sam/Debian/gnat/gnat-3.12p/ada/rts/ instead of /usr/lib/gcc-lib/i486-linux/2.8.1/adainclude/ As an ugly workaround, I can create a symlink from /usr/lib/gcc-lib/i486-linux/2.8.1/adainclude/ into /home/sam/Debian/gnat/gnat-3.12p/ada/rts/ so GDB can find the files, but clearly, the correct solution is to build GNAT in such a way that libgnat.so contains the correct locations for its source files. I'm using Debian 2.3 (woody), kernel version 2.2.14, libc6 version 2.1.3-2, and gdb version 4.18.19990928-1. -Jake
--- End Message ---
--- Begin Message ---Version: 4.4.6-6+rm Dear submitter, as the package gnat-4.4 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/714577 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
