Debugger.THREAD_NOT_STOPPED / Debugger.NONEXISTENT_VALUE string comparisons

The Debugger implementation of THREAD_NOT_STOPPED / NONEXISTENT_VALUE makes us compare the returned value with a string for every result returned. This works fine normally, however the underlying cpp implementation calls `toString` on both values, which can fail with a stack overflow in the case of recursive objects.
I can easily make the debugger crash by trying to get the stack value of an object like:

```haxe
var obj:Dynamic = { a:10, b:null };
obj.b = obj;
```
After setting `obj.b` as `obj`, trying to get the stack value of this will consistently crash because of this string compare.

At first I thought about making an issue about `toString` sometimes crashing because of stack overflow - and I still think this is an issue - however it seems to me that using strings for these kinds of special values is not a great approach, as these values may occasionally (though I reckon rarely :) ) happen in user code, and value comparisons are always slower anyway. It seems to me that it would be both faster and easier to check for a specific control object (e.g. `static var THREAD_NOT_STOPPED = {};`) instead

Inizia con l’implementazione di Debugger di THREAD_NOT_STOPPED e NONEXISTENT_VALUE, quindi riproduci il problema usando l’oggetto Haxe ricorsivo mostrato nell’issue. Il lavoro è completato quando il recupero del suo valore dallo stack non va più in crash a causa della conversione in stringa ed entrambi i valori speciali rimangono distinguibili dai normali valori dell’utente.

Scritto dal modello di indicizzazione a partire dal testo della issue.