Then first create a subclass of DebugAction.
Look for example at��DoesNotUnderstandDebugAction. There are a lot of subclasses of ��DebugAction in the image.
Debugging actions have #appliesToDebugger:. This method controls whether or not the action is loaded by the debugger.
For example DoesNotUnderstandDebugAction is only loaded when the top context is created because of #doesNotUnderstand error.
If you want your action to be present all the time then override #enabled. Look at��FullStackDebugAction.

The second step is to load the previous actions in a debugger.
To load them in the SpecDebugger add to the class side a method annotated with��<debuggingAction>.
To have them in the gt debugger use��<gtDebuggingAction>.
To have them in the pre debug window��<preDebuggingAction>.

This cover more or less what's currently available.

Let me know how it goes.

Cheers,
Andrei



On Thu, May 7, 2015 at 6:10 PM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Next to buttons. I want to make an indicator for a selected method.

Buy the way, can you direct me at where should I start to look in GTDebugger. Because I���m quite new with it.

Uko


On 07 May 2015, at 16:58, Andrei Chis <chisvasileandrei@gmail.com> wrote:

Where do you want these actions to be placed?
In the menu of the stack or next to the stepInto/Over etc buttons?

Cheers,
Andrei

On Thu, May 7, 2015 at 4:36 PM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi,

is it possible to have a debugger action specific for selected context? I.e. define label, icon, whether the action is visible depending on the selected context?

Uko