See this document in CiteSeerX!

A Generic Approach to Monitor Program Executions (1999)  (Make Corrections)  (5 citations)
Erwan Jahier, Mireille Ducassé
International Conference on Logic Programming



  Home/Search   Context   Related

 
View or download:
irisa.fr/lande//ja...ahier_iclp99.ps.gz
irisa.fr/local/lan...ejmdiclp99.ps.gz
Cached:  PS.gz  PS  PDF   Image  Update  Help

From:  irisa.fr/lande/ducasse (more)
(Enter author homepages)

Rate this article: (best)
  Comment on this article  
(Enter summary)

Abstract: Monitoring requires to gather data about executions. The monitoring functionalities currently available are built on top of ad hoc instrumentations. Most of them are implemented at low-level; in any case they require an indepth knowledge of the system to instrument. The best people to implement these instrumentations are generally the implementors of the compiler. They, however, cannot decide which data to gather. Indeed, hundreds of variants can be useful and only end-users know what they... (Update)

Context of citations to this paper:   More

...buggy program. The same mechanisms have also been used as the basis of a generic facility for monitoring the executions of Mercury programs [10]. We have found the time and space costs of enabling debugging in Mercury programs to be within acceptable limits. Just enabling...

...user may indeed be discussed. A trace, however, can be the basis of automated tools, as we have shown for debugging [7] or monitoring [10]. In general, automated dynamic analysis needs an execution 1 model to be based upon and Byrd s box model is a good candidate for Prolog....

Cited by:   More
Symbolic Profiling for Multi-Paradigm Declarative Languages - Albert, Vidal (2002)   (Correct)
Specifying Prolog Trace Models with a Continuation.. - Jahier, Ducassé.. (2000)   (Correct)
Specifying Byrd's Box Model with a Continuation Semantics - Jahier, Ducassé.. (2000)   (Correct)

Active bibliography (related documents):   More   All
0.7:   Generic Program Monitoring by Trace Analysis - Jahier, al. (2002)   (Correct)
0.5:   An automated debugger for Mercury - Morphine 0.1 User and.. - Ducassé, Jahier   (Correct)
0.5:   An automated debugger for Mercury - Opium-M 0.1 User and.. - Ducassé, al.   (Correct)

Similar documents based on text:   More   All
0.2:   Specifying Trace Models With a Continuation Semantics - Jahier, Ducassé   (Correct)
0.2:   The implementation technology of the Mercury debugger - Somogyi, Henderson (1999)   (Correct)
0.2:   OPIUM: An Extendable Trace Analyser for PROLOG - Ducassé (1997)   (Correct)

Related documents from co-citation:   More   All
4:   Tracing Prolog programs by source instrumentation is efficient enough (context) - Ducass'e, Noy'e - 2000
3:   What's in a trace: The box model revisited - Tobermann, Beckstein - 1993
3:   An overview of prolog (context) - Nadathur, Miller - 1988

BibTeX entry:   (Update)

Erwan Jahier and Mireille Ducasse. A generic approach to monitor program executions. In Proceedings of the Sixteenth International Conference on Logic Programming, Las Cruces, New Mexico, 1999. http://citeseer.ist.psu.edu/jahier99generic.html   More

@inproceedings{ jahier99generic,
    author = "Erwan Jahier and Mireille Ducasse",
    title = "A Generic Approach to Monitor Program Executions",
    booktitle = "International Conference on Logic Programming",
    pages = "139-153",
    year = "1999",
    url = "citeseer.ist.psu.edu/jahier99generic.html" }
Citations (may not include all citations):
386   ATOM: A system for building customized program analysis tool.. (context) - Srivastava, Eustace - 1994
130   Optimally profiling and tracing programs - Ball, Larus - 1992
43   ATOM: A flexible interface for building high performance pro.. (context) - Eustace, Srivastava - 1995
41   an efficient purely declarative logic programming language (context) - Somogyi, Henderson et al. - 1996
39   Understanding the control flow of Prolog programs (context) - Byrd - 1980
33   International Thomson Computer Press (context) - Beizer, techniques et al. - 1990
25   concurrent checking of pointer and array accesses in C progr.. (context) - Patil, Fischer - 1997
22   Predicting where faults can hide from testing (context) - Voas, Morell et al. - 1991
20   Monitoring semantics: a formal framework for specifying (context) - Kishon, Hudak et al. - 1991
20   A debugger for Standard ML - Tolmach, Appel - 1995
14   the limit of control flow analysis for regression test selec.. - Ball - 1998
8   Special issue on Synthesis (context) - Ducass'e, An et al. - 1999
7   A lightweight architecture for program execution monitoring - Jeffery, Zhou et al. - 1998
6   Tracing Prolog programs by source instrumentation is efficie.. (context) - Ducass'e, Noy'e - 2000
5   http://www.cs.mu.oz.au/research/mercury (context) - Henderson, Conway et al. - 1999
3   User and Reference Manuals (context) - Ducass'e, Jahier - 1999
2   A layered model for building debugging and monitoring tools (context) - Ho, Olsson - 1996
1   Un traceur d'ex'ecutions de programmes ne sert pas qu'au d'e.. (context) - Jahier, Ducass'e - 1999

Documents on the same site (http://www.irisa.fr/lande/ducasse):   More
DDB trees: a basis for deductive database explanations - Mallet, Ducassé (1997)   (Correct)
Implementation Technologies for Programming Languages based on.. - Sagonas   (Correct)
Analysis of Failing Prolog Executions - Ducasse (1992)   (Correct)

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC