This was recently reported ( bug 298303 ), but was first seen with Eclipse 3.4 ( bug 218881 ).
It will not be fixed yet.
The main problem is that the debugging plugins are not loaded yet, so nothing happens when the handler is activated (although the SDK knows about the key combination).
And this is a regression from Eclipse3.3
This is definitely a (very annoying) regression from 3.3. This was one of the first things I noticed when upgrading to 3.4.
Yes, we fixed some bugs in 3.4 that eagerly loaded debugging plugins (among other plugins) ... but this facet of debugging works (for now) with loaded plugins.
source share