Inexact Floating Point Result Exception is Non Continuable

Author	Message
	float inexact result An error I've never seen before, and I'm not sure what to look for: "float inexact result"   Crash happens only after program has exited and only when compiled. "float inexact result" was the error shown in VC++ debugging. The error shown in Windows varies. I can't think of anything I've changed. In fact the program works fine, but will crash on exit even if I do nothing but open the program and then close it. The "Remove floating point error checks" compile option is selected, but I always select that.   (I've been Googling this but mostly only turning up links to "bigresource.com", which seems to be an operation partnering with Google. I haven't been able to get that site to work at all. Lots of relevant questions, but no answers posted. Maybe it requires script... I don't know.) O.T.: I've just noticed that my copy of Win7 RC doesn't see any FAT32 data partitions! Is that a "feature" of Win7? Or maybe it's part of Microsoft's gradual disablement plan for the RC?
Fri, 31 Aug 2012 03:13:43 GMT
Nobod #2 / 11	float inexact result Quote: > An error I've never seen before, and I'm not > sure what to look for: > "float inexact result" This has nothing to do with floating points. See this article: INFO: Visual Basic Uses Exception Code 0xC000008F as Internal Exception Code http://support.microsoft.com/default.aspx?scid=kb;en-us;232829
Fri, 31 Aug 2012 02:20:05 GMT
Nobod #3 / 11	float inexact result Quote: >> An error I've never seen before, and I'm not >> sure what to look for: >> "float inexact result" > This has nothing to do with floating points. See this article: > INFO: Visual Basic Uses Exception Code 0xC000008F as Internal Exception > Code > http://support.microsoft.com/default.aspx?scid=kb;en-us;232829 One possible reason is binary compatibility. What the article is saying that a property or method failed for some reason.
Fri, 31 Aug 2012 02:30:52 GMT
mayayan #4 / 11	float inexact result Quote: > One possible reason is binary compatibility.  It's a plain EXE, not an ActiveX EXE. Quote: > What the article is saying that > a property or method failed for some reason.   Thanks. That doesn't tell me much, but it saves wasted time chasing after floating point issues. I guess I should look at the forms unloading.
Fri, 31 Aug 2012 03:49:33 GMT
ralp #5 / 11	float inexact result On Sun, 14 Mar 2010 14:49:33 -0500, "mayayana" Quote: >> One possible reason is binary compatibility. > It's a plain EXE, not an ActiveX EXE. In that case it still amounts to essentially the same thing. Often just a project clean-up will take care of the problem. Full compile, exit, delete extraneous files, etc. (delete any OCAs laying around in particular). -ralph
Fri, 31 Aug 2012 04:07:39 GMT
Nobod #6 / 11	float inexact result Quote: >> One possible reason is binary compatibility. > It's a plain EXE, not an ActiveX EXE. I meant components that you are using. Also, do you do any subclassing in this program? If so, try disabling it and see if the error goes away.
Fri, 31 Aug 2012 11:15:58 GMT
mayayan #7 / 11	float inexact result Quote: > >> One possible reason is binary compatibility. > > It's a plain EXE, not an ActiveX EXE. > I meant components that you are using. No components. No dependencies. Quote: > Also, do you do any subclassing in this program? If so, try disabling it and > see if the error goes away.    I am using a number of self-subclassing buttons based on userControls, but it's something I've used before. I could try taking those out if I don't find another answer, but it wouldn't be easy. And this doesn't seem like a subclassing bug, since it's not hapening in the IDE and only happens in the compiled program after it's quit.    I found one discussion online where someone suggested that a call to an outside DLL might be at fault -- something that the EXE is unloading but that doesn't get unloaded in the IDE. But again, I haven't added anything like that and the code used to work fine.    Stranger still, I seem to have got it fixed now in Win98. I'm testing on 98/XP/7. Trouble is, I don't know how I fixed it on 98. I tried waiting longer to release a class in use, but I can't actually find a reason why that would affect anything. And that "fix" doesn't work on XP/7.
Fri, 31 Aug 2012 13:51:23 GMT
mayayan #8 / 11	float inexact result I figured this out, though it still doesn't seem to make sense.   I'm using custom buttons that involve an Image control on a userControl. Self- subclassing with Paul Caton's code. Also using TrackMouseEvent to get hover. I've done this quite a bit with no problems. It turns out that the crash happens when two things are true: * The program close sub is called from a custom button click event. * The close sub ends with "End".   I never ran into this before because I've never used a custom button to close the program. I've closed from the Control Box and it works fine. Even if I unsubclass the exit button in its own click event, before calling the program close sub, it still crashes.   I know that "End" is not recommended. I like to use it for insurance, the logic being that if I've really cleaned up then End is OK. In tests I can tell that all buttons have ubsubclassed before quitting, and the program seems to be fully unloaded without End, but I still don't understand why this should be a problem. I'm fine with not using End, but I'd like to be certain I'm not leaving something in memory.   In some scenarios I've stopped the problem in Win98, though I'm not exactly sure how. Is it possible that VB just needs a little extra time for something, despite having fully unloaded, and that I'm cutting it short by using End? Quote: > >> One possible reason is binary compatibility. > > It's a plain EXE, not an ActiveX EXE. > I meant components that you are using. > Also, do you do any subclassing in this program? If so, try disabling it and > see if the error goes away.
Sat, 01 Sep 2012 02:24:16 GMT
dpb #9 / 11	float inexact result Quote: > I figured this out, though it still doesn't > seem to make sense. ... > * The program close sub is called from a > custom button click event. > * The close sub ends with "End". ... Quote: >   I know that "End" is not recommended. I like > to use it for insurance, the logic being that if > I've really cleaned up then End is OK. Bad idea... ... Quote: >   In some scenarios I've stopped the problem in > Win98, though I'm not exactly sure how. Is it > possible that VB just needs a little extra time > for something, despite having fully unloaded, > and that I'm cutting it short by using End? ... Something like that I'd say is quite likely. End is "NOW!"; anything scheduled but not executed yet is possibly cannon fodder, I'd think it possible all sorts of race conditions and outright failures could arise under various scenarios w/ differing OS levels/patches/etc... --
Sat, 01 Sep 2012 04:14:29 GMT
mayayan #10 / 11	float inexact result Quote: > End is "NOW!"; anything scheduled but not > executed yet is possibly > cannon fodder, I like that metaphor. :)  Everything seems to be getting cleaned up OK without End so I guess I'll just leave it out and assume that the button clicked has some lag in being able to unload. Thanks.
Sat, 01 Sep 2012 05:55:15 GMT
Nobod #11 / 11	float inexact result Quote: >> End is "NOW!"; anything scheduled but not >> executed yet is possibly >> cannon fodder, > I like that metaphor. :) > Everything seems to be getting cleaned up > OK without End so I guess I'll just leave it > out and assume that the button clicked has > some lag in being able to unload. Thanks. It seems that VB does some cleanup even after forms are unloaded. Perhaps it does some cleanup after seeing WM_QUIT, or after the message loop is terminated. Every GUI app or GUI thread has a message loop, including VB apps. http://en.wikipedia.org/wiki/Message_loop_in_Microsoft_Windows In the loop, DispatchMessage() is the one that calls your WindowProc for every message. Most of the time GUI apps are hanged in the call to GetMessage(), and the loop only exits when all forms are loaded and WM_QUIT is posted. This is basically how Windows apps work.
Sat, 01 Sep 2012 06:51:31 GMT

delgadoenation1969.blogspot.com

Source: http://computer-programming-forum.com/72-visual-basic-vb/d5e4b15ea392d93a.htm

Share this post