1. Overview
  2. Debugging workflow
  3. Debugging workflow: CI
  4. Basic interface
  5. Visualizing control flow
  6. Call stacks
  7. Explaining dataflow
  8. Multiprocess
  9. Search box
  10. Source files
  11. Condition and print expressions
  12. Toolbox
  13. Alerts
  14. Application logs
  15. Callees
  16. View operators
  17. Notebook
  18. Instruction execution
  19. Javascript
  20. Browser UI integration
  21. Screenshots
  22. Additional views
  23. GDB
  24. System debug info
  25. Compiler issues
  26. The Pernosco vision
  27. Related work


Events such as assertion failures, test failures and fatal signals are likely to be of special interest to developers. Pernosco collects such events into an "alerts" view. When the user starts a Pernosco session, the debugger automatically focuses on the first alert to kickstart the debugging process.

Pernosco enhances the presentation of alerts using application-specific knowledge. For example, Firefox "reftests" fail when two images that should be the same are actually different. In the alerts for those failures, Pernosco shows both images and lets developers examine the differences and click on pixels to trace the data flow leading to a pixel.