[Seaside] Re: The session in the debugger
Klaus D. Witzel
klaus.witzel at cobss.com
Fri Feb 9 19:58:29 UTC 2007
have a look at the two new changesets which I added to
DoItWithContextVariable-kwl.1.cs resolves accessing the context of the
debuggee, as discussed with Lukas.
WADynamicVariable-kwl.1.cs uses (DoItWithContextVariable raiseSignal) just
for accessing the context of the debuggee (if it needs so).
Please test evaluation of (self session) from the context pane of the
debugger, also other dynamic variables if you have some.
Thank you Lukas for participating in the solution. I think that the above,
since it is implemented by WADynamicVariable just when it searches for
itself on the stack, does not impose any problem on any other exception
handling, unwind or process manipulation.
P.S. No other change set is needed.
On Wed, 07 Feb 2007 22:26:14 +0100, Lukas Renggli wrote:
>> Stack search now added and (surprise! :) now it shows seaside's session
>> the debugger (labelled aSession class name).
> I don't think this is quite what we want: We would like to be able to
> select any part of the code in the code pane and evaluate it. This
> code might directly or indirectly do a stack-lookup for dynamic
> variables such as (but not limited to) the current session. This does
> not work right now, as a doIt is not executed in the context of the
> Now this is a little bit tricky. When processing a doIt the execution
> stack in the debugger should be chained with the one from the doIt,
> but otherwise not touched or unwound. I already do chain two execution
> stacks with Continuation>>#invoke:, but in the debugger this seems to
> be slightly more tricky ...
More information about the Seaside