Mireille Ducassé
- 1.P. Bates. Debugging heterogeneous distributed systems using event-based models of behavior. In Workshop on Parallel and Distributed Debugging, pages 11-22. Sigplan Notices, 24(l), January 1989. Google Scholar
Digital Library
- 2.J. Bovey, M. Russel, and 0. Folkestadt. Direct manipulation tools for Unix workstations. In EUUG Aukmn'88, pages 311-319, October 1988.Google Scholar
- 3.D. Cohen, M. S. Feather, K. Narayanaswaniy, and S. Fickas. Automatic monitoring of software requirements. In 19th International Conference on Software Engineering, pages 602-603. IEEE Press, 1997. Google ScholarDigital Library
- 4.M. Consens, M. Hasan, and A. Mendelzon. Visualizing and querying distributed event traces with Hy+. In Applications of Databases, First International Conference, pages 123-141. Springer, Lecture Notes in Computer Science, Vol. 819, 1994.Google Scholar
- 5.M. Ducass& Abstract views of Prolog executions in Opium. In International Logic Programming Symposium, pages 18-32, October 1991. MIT Press.Google Scholar
- 6.M. Ducasd. Opium: An extendable trace analyser for Prolog. The Journal of Logic programming, 1999.Google Scholar
- 7.M. Ducassh and J. NoyB. Logic programming environments: Dynamic program analysis and debugging. The Journal of Logic Programming, 19/20:351-384, May/July 1994.Google ScholarCross Ref
- 8.M. Golan and D. Hanson. DUEL- A very high-level debugging language. In Winter USENIX Technical Conference, January 1993.Google Scholar
- 9.C. LeDoux. A knowledge-based system for debugging concurrent software. PhD thesis, University of California, Los Angeles, 1985. Google ScholarDigital Library
- 10.R. Lencevicius, U. HGlzle, and A. Singh. Querybased debugging of object-oriented programs. In Proceedings of the OOPSLA Symposium, 1997. Google ScholarDigital Library
- 11.A. Malony, D. Hammerslag, and D. Jablonowski. Traceview: A trace visualization tool. IEEE Software, pages 19-28, September 1991. Google ScholarDigital Library
- 12.M. Powell and M. Linton. A database model of debugging. In ACM SIGSOFT/SIGPLAN Software Engineering Symposium on high-level debugging, pages 67-70. ACM, March 1983. Google ScholarDigital Library
- 13.S. Reiss. Trace-based debugging. In First Workshop on Automated and Algorithmic Debugging, volume 749 of Lecture Notes in Computer Sciences, pages 305-314, 1993. Springer-Verlag. Google ScholarDigital Library
- 14.R. Stallman. Emacs: The extensible, customizable, self-documenting display editor. Sigplan Notices, 16(6), June 1981. Google ScholarDigital Library
- 15.R. Stallman and R. Pesch. Debugging with GDB, the GNU Source-level debuger. The Free Software Fondation, Inc, 4.09 edition, April 1993.Google Scholar
- 16.K. Templer and C. Jeffery. A configurable automatic instrumentation tool for ANSI C. In Automated Software Engineem'ng Conference, 1998. Google ScholarDigital Library
- 17.P. Winterbottom. Acid: a debugger built from a language. In Winter USENIX Technical Conference, pages 211-222, 1994.Google Scholar
- 18.Y. Yamane. Event query based debugging. PhD thesis, University of Washington, 1997. Google ScholarDigital Library
Index Terms
- Coca: an automated debugger for C
Recommendations
Automated atomicity-violation fixing
PLDI '11Fixing software bugs has always been an important and time-consuming process in software development. Fixing concurrency bugs has become especially critical in the multicore era. However, fixing concurrency bugs is challenging, in part due to non-...
Automated atomicity-violation fixing
PLDI '11: Proceedings of the 32nd ACM SIGPLAN Conference on Programming Language Design and ImplementationFixing software bugs has always been an important and time-consuming process in software development. Fixing concurrency bugs has become especially critical in the multicore era. However, fixing concurrency bugs is challenging, in part due to non-...
A debugging strategy based on the requirements of testing: Research Articles
Seventh European Conference on Software Maintenance and Reengineering (CSMR 2003)Testing and debugging activities consume a significant amount of the software development and maintenance budget. To reduce this cost, the use of testing information for debugging purposes has been advocated. In general, heuristics are used to select ...
Comments