Release version runtime error debugging
Hi everybody !
My problem is as following:
A compiled release version of my VB6 application is crashing during runtime with the runtime error code 5 .
Within the IDE it is not happening, so I don't know on which line of code this is happening.
My question :
Is it possible to cause the release version to indicate to me which code address was faulty , in order to be able to use the symbolic debug info file in VC++ and pinpoint the problematic code ?
Please help... rubiCube
[557 byte] By [
rubiCube] at [2007-11-18 2:14:18]
# 1 Re: Release version runtime error debugging
5 is a very low error number...it leads me think about some basic operation in the virtual machine itself...Ie: did you tried some optimization, like assuming no aliases? Then try compiling with optimization only for fast code or small code or even no optimization at all.
Try also a "run with full compile in ide"
then, if non of the above helps,
you might try with wriying some more code in your app.
on error resume next
and with
if err.number<>0 then
msgbox Err.description & "ThishappededHere: your sub"
end if
# 2 Re: Release version runtime error debugging
Thank you for your suggestions .
As a matter of fact, the release version of my program has no problem at all on any of the machines I installed it to . The problem is that the release version was sent to somebody in Korea , and therefore is it impossible for me to reproduce the error in the IDE , because it has probably smth. to do with his regional settings.
But I'll try to do what you advised me to do (like also a special log which will be saving the desired information, or as you said , a msgBox with the function name and line number) . Anyways , it's going to be hard work ...
Thanx
# 3 Re: Release version runtime error debugging
Might I suggest going out to the MS knowledge based and query for that error code? It is a specific error and you know it's VB ...
M Owen at 2007-11-10 0:04:39 >
# 4 Re: Release version runtime error debugging
Dear M. Owen
You might suggest it , of course , but my question was not about the error code itself .
I am asking about the way I could cause the VB release version to indicate to me , where exactly ( at what code address) the fault happened, because the only msg that is put out is a msgBox with only an OK button to press , no info about the location within the code (like in VC++)
rubiCube
# 5 Re: Release version runtime error debugging
Runtime error 5 is Invalid procedure call or argument
The most likely cause is that the user's regional settings are different from yours and you haven't taken this into account?
Try setting your PC to the same regional settings then run the code in the IDE...
# 6 Re: Release version runtime error debugging
My apologies for misunderstanding ... Yes. The only feasible means would be to include error logging code into your application ... It's too bad you couldn't find out roughly where the error occurred at from the user ...
M Owen at 2007-11-10 0:07:38 >
