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.

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

VCD file is not flushed if stdout is piped into 'less' #877

Closed
veripoolbot opened this issue Feb 3, 2015 · 1 comment
Closed

VCD file is not flushed if stdout is piped into 'less' #877

veripoolbot opened this issue Feb 3, 2015 · 1 comment
Labels
resolution: wontfix Closed; work won't continue on an issue or pull request

Comments

@veripoolbot
Copy link
Contributor


Author Name: Iztok Jeras (@jeras)
Original Redmine Issue: 877 from https://www.veripool.org
Original Date: 2015-02-03


Hi,

I created a bench which outputs a lot of text after the first error, so I piped the output into less like this:

LD_LIBRARY_PATH=/usr/local/lib/ obj_dir/Vrp8_verilator |less

The VCD file is not generated entirely till I scroll to the bottom in the less editor. It seems to stop at about the same time in the simulation where the currently visible error in the editor was generated.

Regards,
Iztok Jeras

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2015-02-03T20:03:44Z


This is the nature of how unbuffered IO works in the OSes, which is required to get reasonable trace performance under normal usage. Sorry.

@veripoolbot veripoolbot added the resolution: wontfix Closed; work won't continue on an issue or pull request label Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: wontfix Closed; work won't continue on an issue or pull request
Projects
None yet
Development

No branches or pull requests

1 participant