Meeting: talking debugger with Jocelyn at ETH - Revision history

Jfiat: /* Organisation */

2007-12-17T11:07:44Z

‎Organisation

Aleitner: /* Meetings */

2007-12-14T15:47:13Z

‎Meetings

Jfiat: breaking long line

2007-12-13T18:19:58Z

breaking long line

Jfiat: breaking long line

2007-12-13T18:19:34Z

breaking long line

Arnofiva: /* Meetings */

2007-12-13T16:10:12Z

‎Meetings

Aleitner: /* Meetings */

2007-12-13T16:08:56Z

‎Meetings

Aleitner at 16:06, 13 December 2007

2007-12-13T16:06:38Z

Mogh: /* Meetings */

2007-12-13T11:07:15Z

‎Meetings

Jfiat at 10:48, 12 December 2007

2007-12-12T10:48:27Z

Jfiat at 10:46, 12 December 2007

2007-12-12T10:46:55Z

@@ Line 9: / Line 9: @@
 = Organisation =
-* To be confirmed soon
 == Date ==
 * arrival: tuesday 18th of December, Zurich HB either at 13h56 or 12h56
@@ Line 22: / Line 22: @@
-References:
+= References =
 * http://dev.eiffel.com/CddBranch
 * http://se.ethz.ch/people/leitner/publications/cdd_leitner_esec_fse_2007.pdf
 * http://portal.acm.org/citation.cfm?id=1082983.1083251
-Please complete the following list with your items:
+= Please complete the following list with your items =
 * General dicussion about the CDD idea
@@ Line 42: / Line 42: @@
    (it doesn't care whether it gets the gui one or the console one).
 **** Is it okay to retrieve the whole application state through ABSTRACT_DEBUG_VALUE's? Seems to become really slow with big applications.
 *** Console debugger crashes (Arno can you provide details please)
 **** TTY debugger seems to have problems when exception in infix features occurs -> not possible to use tty menu anymore
@@ Line 58: / Line 61: @@
 **** How can we use the debugger for it
 ***** old values
 ***** invariants
 **** How can we use ES capture and "Review" for it?
 ** Build system needs
 *** How to do it properly on Windows? (Stefan, please provide details here)
@@ Line 65: / Line 73: @@
   Jocelyn: Those days, I am integrating+updating works from es-make team (Bernd and others) into the trunk,
    this way it should be much more easier to build the EiffelStudio tools. Still in progress.
 ** Guided tour through debugger
 ** Guided tour through build system
 ** Unable to debug ES with ES (only Stefan and Andreas). Maybe Jocelyn can have a quick look.
 ** Capture and Replay
 *** Compare ES Capture and Replay and Sel. Capture and Replay

@@ Line 15: / Line 15: @@
 * tuesday night, hotel, or hosted by ETH people (but not in the streets)
 == Meetings ==
-* tuesday: 14:00 -> 15:00 .. about build process, ...
+* tuesday: 14:00 -> 15:00 .. about build process, ... (Arno)
-* tuesday: 15:00 -> ... : debugger related points
+* tuesday: 15:00 -> ... : debugger related points (Andreas, Arno)
-* wednesday: morning: continuation of debugger related points
+* wednesday: morning: continuation of debugger related points (Andreas, Arno starting at 10)
 * wednesday: afternoon .. Jocelyn will be on train, and ETH can do a final meeting to "compute" all the information ;)

@@ Line 36: / Line 36: @@
 *** How to best do bg extraction of test cases
 **** Is our approach of using the debugger in console mode the right one?
-  Jocelyn: For now, there is GUI debugger, TTY debugger, and I guess CDD debugger, but you are not obliged to be in "console" mode (one can imagine a HTTP debugger, or even a silent debugger)
+  Jocelyn: For now, there is GUI debugger, TTY debugger, and I guess CDD debugger,
   Andreas: The CDD test case extractor must be given an extractor

@@ Line 36: / Line 36: @@
 *** How to best do bg extraction of test cases
 **** Is our approach of using the debugger in console mode the right one?
-  Jocelyn: For now, there is GUI debugger, TTY debugger, and I guess CDD debugger, but you are not obliged to be in "console" mode
+  Jocelyn: For now, there is GUI debugger, TTY debugger, and I guess CDD debugger, but you are not obliged to be in "console" mode (one can imagine a HTTP debugger, or even a silent debugger)
   Andreas: The CDD test case extractor must be given an extractor (it doesn't care whether it gets the gui one or the console one).
- one can imagine a HTTP debugger, or even a silent debugger
+  Andreas: The CDD test case extractor must be given an extractor
 **** Is it okay to retrieve the whole application state through ABSTRACT_DEBUG_VALUE's? Seems to become really slow with big applications.
 *** Console debugger crashes (Arno can you provide details please)
@@ Line 50: / Line 51: @@
 ** Console Menu (again Arno)
 *** Multiple debuggers at the same time (large long term issue)
-  Jocelyn: That might be possible, but this won't be that easy for now, however, I have been changing progressively the design to be more flexible, and to allow that in the future. Maybe ISE could plan this for 6.3 with other major design changes.
+  Jocelyn: That might be possible, but this won't be that easy for now, however,
 *** Prestate capturing
 **** How can we use the debugger for it
@@ Line 59: / Line 62: @@
 *** How to do it properly on Windows? (Stefan, please provide details here)
 *** (by Stefan) well, i am getting used to it. The problems with the updated build scripts is that they might not be compatible with 6.0, which cdd is based on? (i admit i did not try)
-  Jocelyn: Those days, I am integrating+updating works from es-make team (Bernd and others) into the trunk, this way it should be much more easier to build the EiffelStudio tools. Still in progress.
+  Jocelyn: Those days, I am integrating+updating works from es-make team (Bernd and others) into the trunk,
 ** Guided tour through debugger
 ** Guided tour through build system

@@ Line 39: / Line 39: @@
   Andreas: The CDD test case extractor must be given an extractor (it doesn't care whether it gets the gui one or the console one).
   one can imagine a HTTP debugger, or even a silent debugger
 *** Console debugger crashes (Arno can you provide details please)
   Jocelyn: TTY debugger is not perfect (not enough time to work on it), what should be done is
 ) change the "menu like control" by a "shell like control"

@@ Line 7: / Line 7: @@
 * Stefan
 * Arno
 References: