1. Any bug on compiled abort()?
- Posted by akusaya at gmx.net Jan 21, 2006
- 515 views
Hi, Is there any known bug in the compiled version of abort()? A customer has complained to me that he cannot close the program when he click the X button (using win32lib). After some correspondence, I give him a debug version that contains code like this: procedure Window1_onClose (integer self, integer event, sequence params) object td debug("close pressed, going to close...") tulisina(FILE_INA, "tProfDir", getText(tProfDir)) ... tulisina(FILE_INA, "lsPilihUser", getItem(lsPilihUser, 0)) debug("writing settings ok, aborting") abort(0) debug("SHOULD NOT SEE THIS") end procedure setHandler( Window1, w32HClose, routine_id("Window1_onClose")) Then he send me the debug output. The last lines of the output were: 042270156 close pressed, going to close... 042270156 writing settings ok, aborting but still he reported that the program never closes! Is there any solution? Thanks!
2. Re: Any bug on compiled abort()?
- Posted by Robert Craig <rds at RapidEuphoria.com> Jan 22, 2006
- 480 views
akusaya wrote: > Is there any known bug in the compiled version of abort()? No. > A customer has complained to me that he cannot close the program when > he click the X button (using win32lib). After some correspondence, I > give him a debug version that contains code like this: > > > procedure Window1_onClose (integer self, integer event, sequence params) > object td > > debug("close pressed, going to close...") > > tulisina(FILE_INA, "tProfDir", getText(tProfDir)) > ... > tulisina(FILE_INA, "lsPilihUser", getItem(lsPilihUser, 0)) > > > debug("writing settings ok, aborting") > > abort(0) > > debug("SHOULD NOT SEE THIS") > > end procedure > setHandler( Window1, w32HClose, routine_id("Window1_onClose")) > > > Then he send me the debug output. The last lines of the output were: > > 042270156 close pressed, going to close... > 042270156 writing settings ok, aborting > > > but still he reported that the program never closes! Is there any > solution? One thing I see in the code is that it tries to call FreeLibrary() on all open .dll's. I wonder if you opened a .dll, and FreeLibrary is having problems with it. I wonder also, if a "DOS" window is open saying "Press Enter" or something, and not allowing the Windows window to close. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com