ActiveState Community

Handling of break disabled in DGBP protocol

Posted by devinheitmueller on 2007-06-07 07:31
OS: Red Hat / Fedora Core

I have disabled the alarm routine in the perl5db.pl due to a problem I am having with a multithreaded application. However, this does not disable the "break" button in the Komodo GUI. I would have assumed that if I told the debugger that break was disabled in the DGBP feature negotiation that the button would be disabled.

I set the following:

$supportedCommands{break} = 0;
$supportedFeatures{supports_async} = [0, 0, 0];
$settings{supports_async} = [0];

And here is the DGBP feature negotiation confirming break is not supported:

feature_get -n break -i 11
179.<?xml version="1.0" encoding="UTF-8" ?>

However, the button is not disabled.

Is there something else the debugger is keying off of to disable the button? Does Komodo support greying out the button if the target says it does not support the break feature?

Running Komodo 4.1.0 build 278996 on win32-x86.

Thanks,

Devin Heitmueller

There is a bug on this:
ericp | Thu, 2007-06-07 09:57

See http://bugs.activestate.com/show_bug.cgi?id=35000

Yes, we're planning on changing the settings exactly as you
described, and pulling out all async-enabling features in
the debugger code. But this is a known bug.

Please feel free to CC yourself on the bug so you can be
notified on updates.

Excellent
devinheitmueller | Thu, 2007-06-07 10:52

Added self to cc.

It might be worth leaving in the alarm code in the stub, for cases where people know they won't be affected. It's in my opinion a significant feature to take out of the product, although I do understand why it is necessary. At least if it stays in the code but skip_alarm is set to 1 by default a user can override it in cases where he/she know it is safe.

Thanks,

Devin Heitmueller