constraint error: Message: nodes.adb:111 index check failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ghdl (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ghdl
Hi,
This is on Gutsy on amd64; on ghdl package 0.25+gcc4.
the hardy ghdl packages (and gnat base dependencies) that is 0.26+gcc4.
get the same problem.
On compiling my vhdl program (which probably contains a bug in the configuration section) I get a GHDL bug
message as seen below; it should just give me normal errors about my code.
I've also reported this on the ghdl bug tracker:
https:/
(where I've attached the top level source file).
ghdl -a -P../unisim --ieee=synopsys -fexplicit logantest.vhd
logantest.
*******
Please report this bug on http://
GHDL release: GHDL 0.26 (20070408) [Sokcho edition]
Compiled with GNAT Version: 4.2.3 20071019 (prerelease)
In directory: /home/dg/
Command line:
/usr/lib/
Exception CONSTRAINT_ERROR raised
Exception information:
Exception name: CONSTRAINT_ERROR
Message: nodes.adb:111 index check failed
Call stack traceback locations:
0x2b60a169d252 0x2b60a169d412 0x2b60a169d5cd 0x2b60a169d65d 0x416c6f 0x4183ad 0x41f09d 0x41f115 0x4da757 0x4db0c2 0x4dba8d 0x4b5975 0x4b616b 0x412754 0x407491 0x411eb1 0x4128e5 0x406b45 0x2b60a1cbdb42 0x406737
*******
Execution terminated by unhandled exception
Exception name: CONSTRAINT_ERROR
Message: nodes.adb:111 index check failed
Call stack traceback locations:
0x2b60a169d252 0x2b60a169d412 0x2b60a169d5cd 0x2b60a169d65d 0x416c6f 0x4183ad 0x41f09d 0x41f115 0x4da757 0x4db0c2 0x4dba8d 0x4b5975 0x4b616b 0x412754 0x407491 0x411eb1 0x4128e5 0x406b45 0x2b60a1cbdb42 0x406737
/usr/lib/
make: *** [logantest.o] Error 1
Changed in ghdl (Ubuntu): | |
status: | New → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 186260 and any other logs that are relevant for this particular issue.