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

<< Toolbox Application logs >>