gnat-4.9_4.9.0-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 29 May 2014 17:08:07 +0200 Source: gnat-4.9 Binary: gnat-4.9-base gnat-4.9 gnat-4.9-sjlj libgnat-4.9 libgnat-4.9-dbg libgnatvsn4.9-dev libgnatvsn4.9 libgnatvsn4.9-dbg libgnatprj4.9-dev libgnatprj4.9 libgnatprj4.9-d

Bug#749574: marked as done (gnat-4.9: Gnatlink fails with CONSTRAINT_ERROR in gnatlink.adb)

Your message dated Thu, 29 May 2014 21:39:53 + with message-id and subject line Bug#749574: fixed in gnat-4.9 4.9.0-2 has caused the Debian Bug report #749574, regarding gnat-4.9: Gnatlink fails with CONSTRAINT_ERROR in gnatlink.adb to be marked as done. This means that you claim that the pro

Processing of gnat-4.9_4.9.0-2_amd64.changes

gnat-4.9_4.9.0-2_amd64.changes uploaded successfully to localhost along with the files: gnat-4.9-base_4.9.0-2_amd64.deb libgnat-4.9_4.9.0-2_amd64.deb libgnat-4.9-dbg_4.9.0-2_amd64.deb libgnatvsn4.9-dev_4.9.0-2_amd64.deb libgnatvsn4.9_4.9.0-2_amd64.deb libgnatvsn4.9-dbg_4.9.0-2_amd64.deb

Bug#749574: gnat-4.9: Gnatlink fails with CONSTRAINT_ERROR in gnatlink.adb

I have found the reason why upstream gnatlink appears to work where Debian's gnatlink fails. Consider this program: with Ada.Text_IO; procedure A is type String_Access is access String; G : constant String (3 .. 5) := "345"; H : constant String_Access := new String'(G); begin if G (1

Bug#749574: gnat-4.9: Gnatlink fails with CONSTRAINT_ERROR in gnatlink.adb

I have been able to fix this problem by patching gnatlink.adb; patch attached. I am puzzled by your report that this bug is not triggered in the home-built upstream gnat-4.9 snapshot (gcc-4.9-20140112). Could you please try the following in the directory containing mai_read_config.adb: cat > gdb