$dumpvars frequently does not have an $end

[dvvgit]

In many practical VCD files, the $dumpvars simply starts the value changes, and there is no matching $end. If this is the case, the parser dies when the first time record, say, #1234, is encountered, with a mysterious exception '1234'. One possible solution is to check for # in vcd_value_change. I can send you a proposed diff if you are interested (did not figure the way to attach it here).

Sincerely, Dima.

[Nic30]

Hello @dvvgit ,

I can send you a proposed diff if you are interested

That would be nice, you can attach it to comment using just drag and drop to a message box.
But it would be more professional to just create a pull request if you already have a fix for this issue.

Best regards, Nic30.

[Nic30]

@dvvgit Nice. Now, do you have at least some simple example so we can add it to tests?

[dvvgit]

Here is a shortened version of the failing file.

test.txt