Debugging in Eclipse broken after 1.99.47

[mtbgithub]

As I reported yesterday in xda (http://forum.xda-developers.com/showthread.php?p=50527433), upgrading from 1.99.47 to 51 (and 52) broke debugging in Eclipse for me, causing some form of infinite loop in the xposed framework to be reported in Eclipse.

I subsequently reported this in the xposed thread on xda (http://forum.xda-developers.com/showthread.php?p=50536931) and got a reply where rovo89 has suggested the following...

"A module has hooked the constructor of Object. When this happens, crashes like this have to be expected.
If the problem only occurs with newer versions of XPrivacy, I think we can assume that it is the culprit. I'm sure that M66B wouldn't do this intentionally so it might be a bug in his hooking framework (on top of Xposed's API). I don't think I can help here, but it might help him if you can reduce the range where the bug has been introduced by testing other intermediate versions one by one.

Oh, skimming over the change list, this might be the reason: 7bbbe40
Looks like hooking any constructor will also hook the constructors of the super classes, and Object is always a super class."

Please let me know what additional information I can provide, I am naturally happy to continue testing to help you iron out the problem.

Cheers

[M66B]

I have to think @rovo89 for pointing this out, because this is a major bug and indeed an unintended side effect if the referenced commit.