I have just seen that there are in fact empty memory addresses provided by the Max debuger. BLIde may be waiting for a response to the contents, but this response never comes. In your example, the problem happens when you try to expand the item poiting to the address $00000000 wich is an item pointing to NULL. I think I can fix this very easily for the next version, but I'm not sure if this may be the only scenario where the debuger just ignores the request of data... I'll add some security checks to prevent things not getting populated.
I'll get back to you as soon as I've found a possible solution. Do you mind if I send you an email?
I'll get back to you as soon as I've found a possible solution. Do you mind if I send you an email?