Package: libgnat-4.1 Version: 4.1.1-19 Severity: normal
Certain facilities, such as the debugging storage pool, cannot really be used in the debugger to their full capability because the system as it ships does not allow you to set a breakpoint within the GNAT library code. The reason for this is that libgnat-4.1 is optimized and stripped, so the debugger treats function calls to GNAT library functions as opaque. There is a static library that is not stripped, but it is not usable in all circumstances, because to make use of it appears to require that *all* libraries be static. For a program of any real complexity (e.g., gnat-gps), this is hard to achieve. The right answer, I think, is to do what other library maintainers do: generate a debugging version of the library and place it into the /usr/lib/debug hierarchy. When someone wants to include the library in their debugging efforts, they need only place /usr/lib/debug in their LD_LIBRARY_PATH. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-2-amd64 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libgnat-4.1 depends on: ii gnat-4.1-base 4.1.1-19 The GNU Compiler Collection (gnat ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-19 GCC support library libgnat-4.1 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]