ghwdump should handle zero-length signals (#1327)

* Adding a test for issue #1326 to check that ghwdump doesn't crash with a zero-length signal.

* Remove an assertion from ghwlib that prevents zero-length signals.

2 files changed, 35 insertions, 0 deletions

diff --git a/testsuite/gna/issue1326/mytestbench.vhdl b/testsuite/gna/issue1326/mytestbench.vhdl
new file mode 100644
index 000000000..3dbda0d6d
--- /dev/null
+++ b/testsuite/gna/issue1326/mytestbench.vhdl
@@ -0,0 +1,17 @@
+library ieee ;
+
+entity mytestbench is
+end mytestbench;
+
+architecture arch of mytestbench is
+  signal zero_length_array : bit_vector(-1 downto 0);
+begin
+
+  -- Just here so we get a meaningful dump.
+  main_process: process
+  begin
+    wait for 10 ns;
+    wait;
+  end process;      
+
+end arch; 
diff --git a/testsuite/gna/issue1326/testsuite.sh b/testsuite/gna/issue1326/testsuite.sh
new file mode 100755
index 000000000..e6b3262c8
--- /dev/null
+++ b/testsuite/gna/issue1326/testsuite.sh
@@ -0,0 +1,18 @@
+#! /bin/sh
+
+. ../../testenv.sh
+
+analyze mytestbench.vhdl
+elab mytestbench
+
+simulate mytestbench --wave=dump.ghw | tee mytestbench.out
+
+gcc ../../../src/grt/ghwdump.c ../../../src/grt/ghwlib.c -I../../../src/grt/ -o ghwdump
+
+# We're just checking that ghwdump doesn't crash on a zero length signal.
+./ghwdump -ths dump.ghw > dump.txt
+
+rm -f mytestbench.out ghwdump dump.txt dump.ghw
+clean
+
+echo "Test passed"