Hi Dilabor, > Well, a small self contained example that triggers the > bug would be much more helpful, really. For example, > you are not using props in a thread safe way, so > another thread could set it to null after you have > assured yourself that it is not null, but before you > get to call props.get(). >
Hmmm... it's posiible... I wrote a working example (a simple hash table manipulation), but it doesn't fail... Our code is quite complex and I'll need some more time to go deeper in it in order to reproduce the problem.... I'll send it ASAP... Regards, > regards, > > dalibor topic > > __________________________________________________ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com > > _______________________________________________ > kaffe mailing list > [EMAIL PROTECTED] > http://kaffe.org/cgi-bin/mailman/listinfo/kaffe > > -- Alexander Popov Team Leader RTOS&JVM ProSyst Bulgaria [EMAIL PROTECTED] [EMAIL PROTECTED] mobile: +35987663193 icq: 29207350 _______________________________________________ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
