error does not climb up the stack - only on specific computers!
Tech-Archive recommends: Fix windows errors by optimizing your registry
our VB6 app has a function which does not have an error handler;
instead, the error is supposed to climb up the stack to the calling
function, which does have an error handler.
This works fine for all of our beta testers - except one (using a
specific computer). When they encounter an error in that function, the
application crashes with a Kernel32 error.
has anyone encountered this bizzare behavior?
.
Relevant Pages
- Re: analog ZQ
... next higher execution level as if the error had not been trapped at the ... suppose your error handler is prepared to handle a ... "ZQ expression unwinds the stack to another call stack level with a $ZTRAP ... handler-specified stack levels ZQUIT unwinds. ... (comp.lang.mumps) - Re: VB6 Error Handling
... I just need a general error handler that will ... You can define a single function that will be called when ... In this function you get access to the stack ... (microsoft.public.vb.general.discussion) - Re: VB6 Error Handling
... Okay, totally irrelevant .NET debates aside, the answer to your question is that VB6 only minimally supports error handling by bubbling up the call stack. ... This will then trigger the parent's error handler, which can trigger it's parent's, and so on. ... (microsoft.public.vb.general.discussion) - Re: VB6 Error Handling
... They bubble up to the point where your VB code starting running. ... error handler, an error gets back to it, it will go back into the VB runtime, ... contains Form.Show is *not* in effect for the Form_Load event handler of the new ... You can see this in the VB call stack in debug mode, ... (microsoft.public.vb.general.discussion) - Re: analog ZQ
... next higher execution level as if the error had not been trapped at the current level." ... For example, suppose your error handler is prepared to handle a error, but that's not what caused the error, then ZQUIT will allow a higher-level error handler to take over. ... "ZQ expression unwinds the stack to another call stack level with a $ZTRAP error handler. ... The value of expression specifies the number of handler-specified stack levels ZQUIT unwinds. ... (comp.lang.mumps) |
|