Bug#306835: marked as done (gnat: Illegal program not detected, RM 3.6(11))
Your message dated Tue, 02 Mar 2010 01:58:27 +0100
with message-id <87635fo7yk.fsf@ludovic-brenta.org>
and subject line gnat: Illegal program not detected, RM 3.6(11)
has caused the Debian Bug report #306835,
regarding gnat: Illegal program not detected, RM 3.6(11)
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 owner@bugs.debian.org
immediately.)
--
306835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=306835
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gnat
Version: 3.15p-12
Severity: normal
procedure Test_146 is
generic
type T1 is private;
package pak1 is
type T2 is array(1..10) of aliased T1;
end pak1;
type T3 (b: Boolean := False) is null record;
package new_pak1 is new pak1 (T1 => T3); --ERROR: T3 unconstrained
begin
null;
end Test_146;
Some output similar to the following is expected, but GNAT says nothing.
test_146.adb:5:41: Type "T1" of aliased component must be constrained (RM 3.6(11))
test_146.adb:9:39: Actual type "T3" is unconstrained (RM 3.6(11))
gnatmake: "test_146.adb" compilation error
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Versions of packages gnat depends on:
ii binutils 2.15-5 The GNU assembler, linker and bina
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libc6-dev 2.3.2.ds1-20 GNU C Library: Development Librari
ii libgnat-3.15p-1 3.15p-12 The GNU Ada 95 compiler runtime li
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.3.0-1
Fixed in 4.3
--- End Message ---
Reply to: