Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Preproc.so causes segfault during Storable retrieve #1063

Closed
veripoolbot opened this issue May 26, 2016 · 3 comments
Closed

Preproc.so causes segfault during Storable retrieve #1063

veripoolbot opened this issue May 26, 2016 · 3 comments
Assignees
@wsnyder

Comments

@veripoolbot
Copy link
Collaborator

Author Name: G. Aydos
Original Redmine Issue: 1063 from https://www.veripool.org
Original Date: 2016-05-26
Original Assignee: Wilson Snyder (@wsnyder)

I am using Storable [1] to store a Verilog::Netlist object on disk. Retrieving an already saved netlist and working with it goes fine but Preproc.so seems to cause a segfault. I attach an example project and a valgrind log. I am using Verilog-Perl 3.418 and Perl 5.22.2.

[1] http://perldoc.perl.org/Storable.html
@veripoolbot
Copy link
Collaborator Author

Original Redmine Comment
Author Name: G. Aydos
Original Date: 2016-05-26T15:25:47Z

Apparently input.v cannot be uploaded because it is empty. Just create it with:
touch input.v

@veripoolbot
Copy link
Collaborator Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2016-05-27T12:49:59Z

The core dump is fixed in git towards 3.420. However you will now get a warning. The Netlist objects rely on internal C data structures which won't get saved by store/retrieve, so might not be useful to you.

@veripoolbot
Copy link
Collaborator Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2016-07-30T14:05:12Z

In 3.420.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wsnyder wsnyder

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wsnyder @veripoolbot