Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Error when opening a VHDL source after running via hdlcc/runner.py #10

Closed
suoto opened this issue Mar 14, 2016 · 1 comment
Closed

Error when opening a VHDL source after running via hdlcc/runner.py #10

suoto opened this issue Mar 14, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@suoto
Copy link
Owner

suoto commented Mar 14, 2016

Given a configured project and a project file named project.prj, the steps to reproduce are

  1. Build the project with hdlcc/runner.py

    runner.py <path/to/project/file> --clean --build

  2. Wait for the build to finish. There should be a filename called
    .project.prj, which is the cached info of the project file

  3. Launching Vim and to a source inside the project gives the following error

$ vim <path/to/source>
Vim: Caught deadly signal SEGV
  File
  "<path/to/vim-hdl>/autoload/../dependencies/hdlcc/hdlcc/project_builder.py",
  line 287, in _recoverCacheVim: Finished.

      cache = pickle.load(open(cache_fname, 'r'))
      AttributeError: 'module' object has no attribute
      'StandaloneProjectBuilder'
      Segmentation fault

Error is slightly different if the file is opened with gVim

$ gvim <path/to/source>
[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb] Aborting, sorry about that.
vim: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion
`!xcb_xlib_unknown_req_in_deq' failed.
Vim: Caught deadly signal ABRT
@suoto suoto added the bug label Mar 14, 2016
@suoto suoto self-assigned this Mar 14, 2016
@suoto suoto added this to the 0.1 milestone Mar 14, 2016
suoto added a commit that referenced this issue Mar 24, 2016
@suoto
Copy link
Owner Author

suoto commented Mar 28, 2016

Issue is related to hdlcc's cache saving and recovering as described in suoto/hdl_checker/issues/4. Issue will be kept open until hdlcc's is fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant