Capture and replay - Revision history

Manus: Added category

2007-05-30T18:26:04Z

Added category

Sieberst: /* Open Questions */

2007-04-19T07:35:25Z

‎Open Questions

Sieberst: /* Open Questions */

2007-04-19T07:35:06Z

‎Open Questions

Sieberst at 07:34, 19 April 2007

2007-04-19T07:34:19Z

Sieberst: /* Other common errors */

2007-04-18T11:49:47Z

‎Other common errors

Sieberst at 11:46, 18 April 2007

2007-04-18T11:46:51Z

Sieberst at 11:37, 17 April 2007

2007-04-17T11:37:03Z

Sieberst at 09:17, 27 March 2007

2007-03-27T09:17:10Z

Sieberst at 09:11, 27 March 2007

2007-03-27T09:11:14Z

Sieberst at 08:55, 27 March 2007

2007-03-27T08:55:28Z

New page

This is the project page for capture & replay debugging

==Overview==
Capture/Replay should be implemented according to [1]:
*After defining the set of observed classes, an instrumented executable should be generated, that records all interactions between observed and unobserved objects.
*For the replay phase, unobserved classes are replaced with stubs that replay their with the observed classes based on the recorded interactions. Thus it should be possible to replay a run for the set of observed classes.

*Capture/Replay should at least be available for the Workbench (Frozen) C Code. The implementation for melted code is optional. It can't be avoided that parts of the work will depend on the compiler backend that is used. These dependencies should be isolated into separate classes and kept as small as possible.

*The overhead of capture/replay should be measured to see if it could be used in practice.

==References==
[1] Shrinivas Joshi and Alessandro Orso: Capture and Replay of User Executions to Improve Software Quality

← Older revision		Revision as of 18:26, 30 May 2007
Line 1:		Line 1:
		+	[[Category:Testing]]
		+	[[Category:Projects]]
	This is the project page for capture & replay debugging		This is the project page for capture & replay debugging

@@ Line 49: / Line 49: @@
 * Why does Eiffel not support 'real' weak references? IDENTIFIED makes it necessary to modify a class before weak references to its objects are possible. Wouldn't it be possible to keep a table of Eiffel objects, which is ignored when calculating the reachable set of objects, but whose references are updated, when the GC moves objects? Instead of keeping the offset of the table entry (object_id of IDENTIFIED):
 ** an entry per weak reference could be made
-** or an entry per object, but then it would be necessary to lookup in the table before  crating the reference
+** or an entry per object, but then it would be necessary to lookup in the table before  creating the reference

← Older revision		Revision as of 07:35, 19 April 2007
Line 47:		Line 47:

	==Open Questions==		==Open Questions==
−	* Why does Eiffel not support 'real' weak references? IDENTIFIED makes it necessary to modify a class before weak references to its objects are possible. Wouldn't it be possible to keep a table of Eiffel objects, which is ignored when calculating the reachable set of objects, but whose references are updated, when the GC moves objects? Instead of keeping the offset of the table entry (object_id of IDENTIFIED)~~, either a~~ entry per weak reference could be made, or an entry per object, but then it would be necessary to lookup in the table before crating the reference	+	* Why does Eiffel not support 'real' weak references? IDENTIFIED makes it necessary to modify a class before weak references to its objects are possible. Wouldn't it be possible to keep a table of Eiffel objects, which is ignored when calculating the reachable set of objects, but whose references are updated, when the GC moves objects? Instead of keeping the offset of the table entry (object_id of IDENTIFIED):
		+	** an entry per weak reference could be made
		+	** or an entry per object, but then it would be necessary to lookup in the table before crating the reference

← Older revision		Revision as of 07:34, 19 April 2007
Line 45:		Line 45:
	==Other common errors==		==Other common errors==
	* console applications in debug mode can't read from console, if the hosting eiffel studio was started in the background ('estudio &' instead 'estudio'). This is no bug, as '&' detaches the application from the standard input.		* console applications in debug mode can't read from console, if the hosting eiffel studio was started in the background ('estudio &' instead 'estudio'). This is no bug, as '&' detaches the application from the standard input.
		+
		+	==Open Questions==
		+	* Why does Eiffel not support 'real' weak references? IDENTIFIED makes it necessary to modify a class before weak references to its objects are possible. Wouldn't it be possible to keep a table of Eiffel objects, which is ignored when calculating the reachable set of objects, but whose references are updated, when the GC moves objects? Instead of keeping the offset of the table entry (object_id of IDENTIFIED), either a entry per weak reference could be made, or an entry per object, but then it would be necessary to lookup in the table before crating the reference

← Older revision		Revision as of 11:49, 18 April 2007
Line 44:		Line 44:

	==Other common errors==		==Other common errors==
−	* console applications in debug mode can't read from console, if the hosting eiffel studio was started in the background ('estudio &' instead 'estudio')	+	* console applications in debug mode can't read from console, if the hosting eiffel studio was started in the background ('estudio &' instead 'estudio'). This is no bug, as '&' detaches the application from the standard input.

← Older revision		Revision as of 11:46, 18 April 2007
Line 42:		Line 42:

	* gcc: $ISE_EIFFEL/precomp/spec/linux-x86/EIFGENs/base/W_code/preobj.o: No such file or directory --> building of precompiles not successfully finished. Precompile $ISE_EIFFEL.		* gcc: $ISE_EIFFEL/precomp/spec/linux-x86/EIFGENs/base/W_code/preobj.o: No such file or directory --> building of precompiles not successfully finished. Precompile $ISE_EIFFEL.
		+
		+	==Other common errors==
		+	* console applications in debug mode can't read from console, if the hosting eiffel studio was started in the background ('estudio &' instead 'estudio')

← Older revision		Revision as of 11:37, 17 April 2007
Line 36:		Line 36:
	==References==		==References==
	[1] Shrinivas Joshi and Alessandro Orso: Capture and Replay of User Executions to Improve Software Quality		[1] Shrinivas Joshi and Alessandro Orso: Capture and Replay of User Executions to Improve Software Quality
		+
		+
		+	==Common build errors==
		+	Here's a draft of some lessons learned while building eiffel studio:
		+
		+	* gcc: $ISE_EIFFEL/precomp/spec/linux-x86/EIFGENs/base/W_code/preobj.o: No such file or directory --> building of precompiles not successfully finished. Precompile $ISE_EIFFEL.

@@ Line 9: / Line 9: @@
 *The overhead of capture/replay should be measured to see if it could be used in practice.
 ==References==
 [1] Shrinivas Joshi and Alessandro Orso: Capture and Replay of User Executions to Improve Software Quality

← Older revision		Revision as of 09:11, 27 March 2007
Line 12:		Line 12:
	==References==		==References==
	[1] Shrinivas Joshi and Alessandro Orso: Capture and Replay of User Executions to Improve Software Quality		[1] Shrinivas Joshi and Alessandro Orso: Capture and Replay of User Executions to Improve Software Quality
		+	[[Image:Schedule 2007-03-27.png]]