Talk:Digging memory leaks of EiffelStudio - Revision history

Manus at 09:52, 6 April 2007

2007-04-06T09:52:50Z

Ericb at 07:16, 6 April 2007

2007-04-06T07:16:52Z

Manus at 12:57, 5 April 2007

2007-04-05T12:57:08Z

Ericb: mem map for debugged applications?

2007-04-03T07:35:13Z

mem map for debugged applications?

Jfiat at 13:17, 2 April 2007

2007-04-02T13:17:16Z

New page

--[[User:Jfiat|Jocelyn]] 15:17, 2 April 2007 (CEST)
I think "memory leaks" is not only about "once" feature, it may occurs with C interfacing too (when objects might by adopted and frozen for C purpose), and there is also the case with graphical interface using "agent" keeping references to unused objects.

@@ Line 5: / Line 5: @@
 Is there a way to get the same kind of window as the GC statics mem map window for the application currently debugged in EiffelStudio debugger (rather than for the EiffelStudio application itself)? It would be much more convenient than having to pollute our application code with calls to MEMORY.memory_map, in the same vein we don't pollute our code with ''io.put_string'' but rather use the debugger object browser to inspect values.
-'''--[[User:Manus|manus]] 14:57, 5 April 2007 (CEST)''' At the moment, the memory map can be done within one application. Doing it in the debugger would not be very efficient at all since it would require EiffelStudio to know about all the objects in the program and in addition causing a leak by keeping track of them. Indeed each time an object is monitored by EiffelStudio, it is not a candidate for garbage collection even if no other objects reference it.
+:'''--[[User:Manus|manus]] 14:57, 5 April 2007 (CEST)''' At the moment, the memory map can be done within one application. Doing it in the debugger would not be very efficient at all since it would require EiffelStudio to know about all the objects in the program and in addition causing a leak by keeping track of them. Indeed each time an object is monitored by EiffelStudio, it is not a candidate for garbage collection even if no other objects reference it.
---[[User:Ericb|Ericb]] 09:16, 6 April 2007 (CEST): I'm just interested in the number of objects per type. Why can't the debugged application send this information to EiffelStudio on request. No need for EiffelStudio to know about each and every object of the application.
+::--[[User:Ericb|Ericb]] 09:16, 6 April 2007 (CEST): I'm just interested in the number of objects per type. Why can't the debugged application send this information to EiffelStudio on request. No need for EiffelStudio to know about each and every object of the application.

← Older revision		Revision as of 07:16, 6 April 2007
Line 6:		Line 6:

	'''--[[User:Manus\|manus]] 14:57, 5 April 2007 (CEST)''' At the moment, the memory map can be done within one application. Doing it in the debugger would not be very efficient at all since it would require EiffelStudio to know about all the objects in the program and in addition causing a leak by keeping track of them. Indeed each time an object is monitored by EiffelStudio, it is not a candidate for garbage collection even if no other objects reference it.		'''--[[User:Manus\|manus]] 14:57, 5 April 2007 (CEST)''' At the moment, the memory map can be done within one application. Doing it in the debugger would not be very efficient at all since it would require EiffelStudio to know about all the objects in the program and in addition causing a leak by keeping track of them. Indeed each time an object is monitored by EiffelStudio, it is not a candidate for garbage collection even if no other objects reference it.
		+
		+	--[[User:Ericb\|Ericb]] 09:16, 6 April 2007 (CEST): I'm just interested in the number of objects per type. Why can't the debugged application send this information to EiffelStudio on request. No need for EiffelStudio to know about each and every object of the application.

← Older revision		Revision as of 12:57, 5 April 2007
Line 4:		Line 4:
	--[[User:Ericb\|Ericb]] 09:35, 3 April 2007 (CEST):		--[[User:Ericb\|Ericb]] 09:35, 3 April 2007 (CEST):
	Is there a way to get the same kind of window as the GC statics mem map window for the application currently debugged in EiffelStudio debugger (rather than for the EiffelStudio application itself)? It would be much more convenient than having to pollute our application code with calls to MEMORY.memory_map, in the same vein we don't pollute our code with ''io.put_string'' but rather use the debugger object browser to inspect values.		Is there a way to get the same kind of window as the GC statics mem map window for the application currently debugged in EiffelStudio debugger (rather than for the EiffelStudio application itself)? It would be much more convenient than having to pollute our application code with calls to MEMORY.memory_map, in the same vein we don't pollute our code with ''io.put_string'' but rather use the debugger object browser to inspect values.
		+
		+	'''--[[User:Manus\|manus]] 14:57, 5 April 2007 (CEST)''' At the moment, the memory map can be done within one application. Doing it in the debugger would not be very efficient at all since it would require EiffelStudio to know about all the objects in the program and in addition causing a leak by keeping track of them. Indeed each time an object is monitored by EiffelStudio, it is not a candidate for garbage collection even if no other objects reference it.

← Older revision		Revision as of 07:35, 3 April 2007
Line 1:		Line 1:
	--[[User:Jfiat\|Jocelyn]] 15:17, 2 April 2007 (CEST)		--[[User:Jfiat\|Jocelyn]] 15:17, 2 April 2007 (CEST)
	I think "memory leaks" is not only about "once" feature, it may occurs with C interfacing too (when objects might by adopted and frozen for C purpose), and there is also the case with graphical interface using "agent" keeping references to unused objects.		I think "memory leaks" is not only about "once" feature, it may occurs with C interfacing too (when objects might by adopted and frozen for C purpose), and there is also the case with graphical interface using "agent" keeping references to unused objects.
		+
		+	--[[User:Ericb\|Ericb]] 09:35, 3 April 2007 (CEST):
		+	Is there a way to get the same kind of window as the GC statics mem map window for the application currently debugged in EiffelStudio debugger (rather than for the EiffelStudio application itself)? It would be much more convenient than having to pollute our application code with calls to MEMORY.memory_map, in the same vein we don't pollute our code with ''io.put_string'' but rather use the debugger object browser to inspect values.