High-Level Debugging Facilities and Interfaces: Design and Developement of a Debug-Oriented I.D.E.

  • Nick Papoylias
Part of the IFIP Advances in Information and Communication Technology book series (IFIPAICT, volume 319)


While debugging in general is an essential part of the development cycle, debuggers have not themselves evolved over the years as other development tools have through the advancement of Integrated Development Environments. In this free-software research project we propose a way to overcome this problem by introducing, designing and developing a high-level debugging system.

High-Level debugging systems are systems that integrate a source - level debugger with other technologies as to extent both the facilities and the interfaces of the debugging cycle. We designed and developed such a system in a debugging-centric IDE, Misha. Misha, introduces among other things: syntax-aware navigation, data-displaying and editing, reverse execution, debugging scripting and inter-language evaluation through the integration of its source-level debugger (gdb) with a full-fledged source parser, data visualisation tools and other free software technologies.


Integrate Development Environment Free Software Foundation Harmonia Project Static Code Analysis Data Visualisation Tool 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 1.
    Akgul, T., Mooney, V.J.: Instruction-level reverse execution for debugging (2002)Google Scholar
  2. 2.
    Begel, A., Graham, S.L.: An assessment of a speech-based programming environment. In: VLHCC 2006: Proceedings of the Visual Languages and Human-Centric Computing, pp. 116–120. IEEE Computer Society, Los Alamitos (2006)CrossRefGoogle Scholar
  3. 3.
    Berkeley. Harmonia project (2009),
  4. 4.
    Boshernitsan, M., Graham, S.L., Hearst, M.A.: Aligning development tools with the way programmers think about code changes. In: CHI 2007: Proceedings of the SIGCHI conference on Human factors in computing systems, pp. 567–576. ACM, New York (2007)CrossRefGoogle Scholar
  5. 5.
    Brooks Jr., F.P.: The mythical man-month (anniversary ed.). Addison-Wesley Longman Publishing Co., Inc., Boston (1995)Google Scholar
  6. 6.
    Visual Studio Developer Center. Visualisers (2009),
  7. 7.
    Ds-emedia. Jbixle, high-level debugger (2006),
  8. 8.
    Ducassé, M., Emde, A.-M.: Opium: a debugging environment for prolog development and debugging research. SIGSOFT Softw. Eng. Notes 16(1), 54–59 (1991)CrossRefGoogle Scholar
  9. 9.
    Ellson, J.: Graphviz, graph visualization software (2009),
  10. 10.
    Free Software Foundation. High-priority projects (2009),
  11. 11.
    Golan, M., Hanson, D.R.: Duel - a very high-level debugging language (1993)Google Scholar
  12. 12.
    Gorla, N., Benander, A.C., Benander, B.A.: Debugging effort estimation using software metrics. IEEE Trans. Software Eng. 16(2), 223–231 (1990)CrossRefGoogle Scholar
  13. 13.
    Menapace, D.M.J., Kingdon, J.: The “stabs” debug format. Cygnus Support (2004)Google Scholar
  14. 14.
    Kitware, B.K.: Gcc xml, extention (2009),
  15. 15.
    Lewis, S.A.: Techniques for efficiently recording state changes of a computer environment to support reversible debugging (2001)Google Scholar
  16. 16.
    Narayanasamy, S., Pokam, G., Calder, B.: Bugnet: Continuously recording program execution for deterministic replay debugging. In: ISCA, pp. 284–295 (2005)Google Scholar
  17. 17.
    Wolfram Research. Instant high-level debugging (2009),
  18. 18.
    Gdb Development Team. Gdbreversible. Debugging (2009),
  19. 19.
    Gdb Development Team. Pythongdb (2009),
  20. 20.
    Teawater. Gdb record patch (2009),
  21. 21.
  22. 22.
    Zeller, A.: Debugging with DDD. Gnu Press (2004)Google Scholar

Copyright information

© IFIP 2010

Authors and Affiliations

  • Nick Papoylias
    • 1
  1. 1.Technical University of CreteChaniaGreece

Personalised recommendations