In my project I creating debug adapter for Visual Studio Code for AngelScript, and sometime have problem.

When I inspecting some variable, context->IsVarInScope return true for it varibale, but context->GetAddressOfVar return nullptr for it, if I do not set returnAddressOfUnitializedObjects to true, because DetermineLiveObjects tell that variable not initialized. But if I use GetAddressOfVar with true for unitialized vars, I got valid address and alive object.

I have not yet been able to identify an obvious pattern, but in my case it was a variable of my internal type “string”, declared inside the loop “for”:

        for (...) {
            string name;
            ... some processing of name
            script.addNamedItem(name, obj, global);
        }

No, I use my own string implementation, but it nothing special - simple value object with constructor, destructor and so on.

There is piece of my code:

array<array<any>@> connectedAddins;
...
many work for build connectedAddins and collect a lot of other information, realy a lot of local variables
...
for (uint k = 0, km = connectedAddins.length; k < km; k++) {
    array<any>@ a = connectedAddins[k];
    IUnknown@ obj;
    string name;
    bool global;
    a[0].retrieve(@obj);
    a[1].retrieve(name);
    a[2].retrieve(global);
    script.addNamedItem(name, obj, global); // << there is breakpoint and check variable 'name'
}

And when I got adsress of name as unitialized var - it valid and containt right string, in my native method addNamedItem I receive right info.

I've encountered the same issue here, with app registered value types that don't have a ctor registered.

If I register a ctor for the type, it's fine.

Thank you, just to confirm that has fixed our issue.

Still quite new to Angelscript, but it's great to see how active the on-going development is.

Mark