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

QL_DOUT, debugging OpenQL #485

Open
jvansomeren opened this issue May 5, 2023 · 0 comments
Open

QL_DOUT, debugging OpenQL #485

jvansomeren opened this issue May 5, 2023 · 0 comments

Comments

@jvansomeren
Copy link
Collaborator

jvansomeren commented May 5, 2023

How is OpenQL debugged?

  • At a crash there is a stack trace.
  • We have QL_{D|I|E|...}_OUT with LOG_LEVEL.
  • And there is sdb/cdb/adb .

QL_DOUT around every statement makes the code less readable but QL_DOUT etc are useful to have an low-entry trace of events to get a first impression of what preceded a crash.
An improvement would be to have pass-level toggles to turn them on/off, or to a particular level; note that this is at compiler run-time, passing options on the compiler command line to particular passes.

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

No branches or pull requests

1 participant