RE: [Java-gnome-developer] Use of destroy()

[Jeffrey M. <Jef...@Br...>]

I would be interested in taking a look at the code that
caused the crash.  I suspect that the call to destory
is not what is causing the problem as we do this often
in other applications.  I am quite curious to locate the
root cause of this problem.  Would it be possible to post 
the code to this list?

-Jeff


> -----Original Message-----
> From: jav...@li...
> [mailto:jav...@li...]On Behalf Of
> Laurent Martelli
> Sent: Wednesday, October 27, 2004 8:54 AM
> To: jav...@li...
> Subject: [Java-gnome-developer] Use of destroy()
> 
> 
> Hi,
> 
> I've spent a few hours tracking down a bug in my application. It
> crashed the JVM when I used escape to close a dialog. It turned out I
> had a DialogListener which called destroy() on the dialog. It was
> really a bad idea because gtk still had references on this dialog. 
> 
> So I'm wondering if it's a good idea to have that destroy() method in
> the java API. It does not seem to be used internally by java-gnome and
> can only give opportunities to the java developper to crash the JVM. 
> 
> -- 
> Laurent Martelli
> la...@ao...                                Java Aspect 
> Components
> http://www.aopsys.com/                          
> http://jac.objectweb.org
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> java-gnome-developer mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/java-gnome-developer
> 

 NOTE: THIS IS A CONFIDENTIAL COMMUNICATION. This transmission is intended
only for the use of the individuals or entity to which it is addressed. If
you are not the intended recipient, or the person responsible for delivering
the message to the intended recipient, please return or delete it
immediately. Although this e-mail and any attachments are believed to be
free of any virus or other defect, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by us for
any loss or damage arising in any way from its unauthorized modification or
use.