Describe how to find source file to debug autos #1471
Assignees
Labels
Comments
|
Original Redmine Comment This is doable, however I think an alternative that exists now may be as useful or more useful. Will shortly (unless you have rewordings) add this to the verilog-auto-inst docs: "To debug what file a submodule comes from, in a buffer with AUTOINST use \[verilog-goto-defun] to switch buffers to the point containing the given symbol (i.e. a submodule name)'s module definition. |
|
Original Redmine Comment Thanks - that should do the trick! |
|
Original Redmine Comment Great, docs pushed to git. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Author Name: David Rogoff
Original Redmine Issue: 1471 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
Hi.
Reading Issue #1464 reminded me of a debug feature that would be great. verilog-auto-inst-template-numbers is very helpful, but would would be really great would be for Verilog-auto to add a comment showing the filename/path where it got the instantiated file. I've been putting together some big, top-level wrapper modules and many sub-modules have versions in multiple directories. It was driving me nuts when ports weren't what I thought they should be until I realized what was going on and had to play with the order of Verilog-library-directories and make sure no other versions were open in emacs buffers.
Would this be easy to add?
Thanks,
David
The text was updated successfully, but these errors were encountered: