Closed eine closed 5 years ago
I think this is now fixed.
Unfortunately, I cannot test it because some other issue was introduced. Now, I get:
Args: ['/usr/local/bin/ghdl-ls', '-v']
Current directory: /vunit/examples/vhdl/array_axis_vcs
2019-06-24 10:12:27,365 [INFO] Args: ['/usr/local/bin/ghdl-ls', '-v']
2019-06-24 10:12:27,365 [INFO] Current directory is /vunit/examples/vhdl/array_axis_vcs
2019-06-24 10:12:27,366 [INFO] reading project file /vunit/examples/vhdl/array_axis_vcs/hdl-prj.json
2019-06-24 10:12:27,366 [INFO] Using options: ['--std=08', '-Pvunit_out/ghdl/libraries/osvvm', '-Pvunit_out/ghdl/libraries/vunit_lib']
raised ERROROUT.OPTION_ERROR : errorout.adb:399
as soon as I open any VHDL file. Syntax highlighting works, but the language server does not.
I can confirm that this is fixed now.
In VSC, I tried the following
hdl-prj.json
in VUnit'sexamples/vhdl/array_axis_vcs
example:Analysis works. I can open
fifo.vhd
, and no errors are reported. This means that context clauses are properly parsed. I can also 'Go to Definition' of e.g.ieee_std_context
,std_logic_vector
orrising_edge
. However, after jumping to the definition, ghdl-ls crashes.Jumping to
rising_edge
first:Note that the server still works. This is not an unrecoverable crash. Further jumps to
rising_edge
,std_logic_vector
orieee_std_context
works ok and it produces no additional error/crashes.Jumping to
ieee_std_context
orstd_logic_vector
first:The crash is unrecoverable:
Connection to server got closed. Server will not be restarted
.