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

Fix "dump-start" in FSDB-mode #3172

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

hngenc
Copy link

@hngenc hngenc commented Nov 19, 2022

When USE_FSDB=1, +dump-start doesn't do anything. It seems VCS just begins dumping signals as soon fsdbDumpfile/fsdbDumpVars is called, rather than waiting for fsdbDumpon.

My simple workaround is to just call fsdbDumpOff explicitly right away. The waveform dumping can resume when fsdbDumpOn is called.

Related issue:

Type of change: bug report

Impact: no functional change (a bug fix)

Development Phase: implementation

Release Notes

When `USE_FSDB=1`, `+dump-start` doesn't do anything. It seems VCS just begins dumping signals as soon `fsdbDumpfile`/`fsdbDumpVars` is called, rather than waiting for `fsdbDumpon`.

My simple workaround is to just call  `fsdbDumpOff` explicitly right away. The waveform dumping can resume when `fsdbDumpOn` is called.
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Nov 19, 2022

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: hngenc / name: Hasan Genc (5dc24ec)

@sequencer sequencer enabled auto-merge (squash) November 19, 2022 07:36
@jerryz123
Copy link
Contributor

Does this affect behavior when dump-start is not specified?

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

Successfully merging this pull request may close these issues.

2 participants