- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If the error occurs at the first line of the subroutine, then my guess is that there is something wrong with the number or type of the arguments. Have you tried running the debugger in the calling routine and verifying that it is passing what the called subroutine expects?
What operating system is your customer running?
Mike D.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There may be stack or other data corruption going on which changes symptom depending on memory layout. Believe it or not, I have also heard from customers that a bad printer driver caused erratic behavior of their programs!
Here's a trick I sometimes employed. Ask the customer to boot their PC into Safe Mode and see if the problem still occurs. If not, then there may be some background program running that is corrupting data.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The program will not link if there is a difference in the number of arguments.
I have checked code and ran in the debugger, checking the arrays and their allocations and everything seems in order.
I cannot get the thing to crash on any of my 3 machines.
Charles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the advice. I have asked her to try in safe mode.
I will send the newest release version and see if I can track down the instruction. I have never generated maps or assembler listings with CVF but I used to do this years ago on mainframes, so I know how to do it (I think!)
If she uses Just in Time Debugging, does she need source to do any good or what?
I can't get Just in Time Debugging to work on my current installation of CVF pro for some reason. I need to run in debug mode (G0=F5) if I want to get into the debugger.
Thanks,
Charles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have solved the problem.
It had to do with an automatic array. The derived type component which specified the size of the automatic array was not initialized, and therefore was highly dependent on the state of the particular machine at the time. I added some code and that moved things around and it then crashed reliably on my machine in both Release and Debug versions. And in the debugger I could see the large negative number in SM%NPAR. So I initialized it to 1 and all is OK now.
Offending code line:
DIMENSION PTEMP(S%M%NPAR),PMTEMP(SM%M%NPAR)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page