This seminar will explore the existing advanced debugging methods -- from interactive debugging tools to experimental methods.
We will have weekly meetings. Each week we will discuss one research paper.
The kickoff-meeting will be on Thursday, 23.10., from 09.15 till 10.00 in room E1 1 1.06
Meetings will be on Thursdays from 09.00 till 10.00 in room E1 1 1.06
News
- 03.11.2014 - Due to conference leave, there will be no session on Thursday 20.11.2014.
List of papers
- Debugging via Slicing
- Program slicing (ICSE'81) - Ezekiel Olamide SOREMEKUN
- Dynamic program slicing (PLDI'90) - Emamurho Juliet Ugherughe
- An efficient relevant slicing method for debugging (FSE'99) - Kai Glauber
- (Dynamic) Tainting
- Penumbra: automatically identifying failure-relevant inputs using dynamic tainting (ISSTA'09) - Birhan Tadele
- Statistical Debugging
- Visualization of test information to assist fault localization (ICSE'02) - Dominic Seyler
A practical evaluation of spectrum-based fault localization (JSS'09) - Sebastian Froede
- Are Automated Debugging Techniques Actually Helping Programmers? (ISSTA'10) - Maximilian Reinert
- Algorithmic Debugging
- Algorithmic Debugging of Java Programs (ENTCS) - Anton Vietrov
- Interrogative Debugging
- Designing the whyline: a debugging interface for asking questions about program behavior (CHI'04) - Martín Ignacio Fallas Hidalgo
- Experimental Debugging>
- Isolating cause-effect chains from computer programs (FSE'02) - Sebastian Kappler
- Locating Faults Through Automated Predicate Switching (ICSE'06) - Björn Mathis
- Debugging via Fixing
- Angelic Debugging (ICSE'11) - Juan Gabriel Umaña Quirós
- Regression Debugging
- Yesterday. my program worked. Today, it does not. Why? (FSE'99) - Alex Schlosser
- DARWIN: An approach to debugging evolving programs (TOSEM'12) - Julian Howes
Registration
We have reached the maximum number of participants for the seminar, and we do not accept any other. The registration is closed.
Passing Requirement
What should you do in order to gain credit points for this course?
- Submit all Summary on time
- Attend the weekly meetings. Up to 2 unexcused absences accepted. Please inform us if you have a valid reason to miss the discussion
- Present one of the papers at the end of semester for 20-25 minutes
- Submit annotated slides of your talk post presentation
Grading Scheme
- Summary: 40%
- Presentation: 40%
- Annotated slides: 20%
Summaries
Each summary should be sent to the mailing list addresses {boehme, galeotti} AT cs.uni-saarland.de by Tuesday 11:59pm.
You can find a sample summary here, together with some suggestions on how to write a summary.
Feedback
At the end of each discussion session we will provide feedback on your summaries and suggestions on how to improve. On top of that, we will also provide
a mini grade which will either be a
- + Very well done summary, and interesting questions
- 0 Good summary. Fulfills all the requirements
- - Summary is lacking important aspects. Should be improved
Students are encouraged to volunteer to summarize and present a 5 minutes talk on a paper to get feedback on their presentation style. Please inform us at least one day before the meeting if you decide to do so.
Contacts
Impressum ● Datenschutzerklärung
<webmaster@st.cs.uni-saarland.de> · http://www.st.cs.uni-saarland.de/edu/adebug/2014/?lang=fr · Stand: 2018-04-05 13:40
|