2015-11-25 17:16 GMT+01:00 Andrei Chis <[email protected]>: > Hi, > > In updating the debuggers from moose to the new API just one small issue > came up: > > - Process>>newDebugSessionNamed:startedAt: hardcodes DebugSession. However > we are using different debugging sessions. > > The class side method #sessionClass of a debugger returns the debugging > session's class. That could be used instead of DebugSession. >
To provide fast fix we can rewrite process method with: Process>>newDebugSessionNamed: aString startedAt: aContext ^Smalltalk tools debugger sessionClass named: aString on: self startedAt: aContext Could you publish issue and slice? In my fixes I try to put single point for debugging. I removed some old methods and clean places where they was used. Session is actual debugger model. And I was think that it is better to always create debugger on it. Now I think that maybe debug session should be internal object for debugger. But it's seems strange. My main target is remote debugger. So I try to investigate all related stuff. What subclasses of DebugSession implement specifically? For what they needed? If we move to GTDebugger completely can we have only debug session class?
