|
From: | Pietro Terna |
Subject: | RE: probes and dropped objects |
Date: | Wed, 06 Sep 2000 17:21:11 +0200 |
You probably mean ops = nil;
-----Message d'origine-----
De : Pietro Terna [mailto:address@hidden]
Envoyé : mercredi 6 septembre 2000 15:06
À : address@hidden
Objet : Re: probes and dropped objects
An auto-reply: a simple solution is that of assigning a null values to the variables related to the dropped objects, like
[ops drop];
drop = nil;
Pietro
At 13.33 06/09/00 +0200, you wrote:
Hi All,
if you open a probe 'on the fly' to an object containing a pointer to a dropped object, you have a segmentation error.
The attached test.tar.gz file contains a simple example of that: if you press 'start' or 'next' and _then_ open a full probe to ObserverSwarm, right clicking on the ObserverSwarm label, the program crashes. Eliminating the drop message to the ops instance of Ops class, the problem disappears.
Any opinion on how to avoid this problem? It's a serious one, because in the debug phase it is quite obvious to open probe to objects 'on the fly', so mapping all the variables and methods of the object: if one of these variables is a pointer to a dropped object ...
Thanks in advance, Pietro
================================== Swarm-Support is for discussion of the technical details of the day to day usage of Swarm. For list administration needs (esp. [un]subscribing), please send a message to with "help" in the body of the message.
[Prev in Thread] | Current Thread | [Next in Thread] |