Mail Archives: djgpp/2000/11/01/05:10:30
On Tue, 31 Oct 2000, Tim Nicholson wrote:
> CWSDMPI -x does remove the problem but it is not as simple as it seems. The
> function works 100% when CWSDMPI -x or Windows is used but fails otherwise.
This clearly suggests a problem with a garbled pointer.
> However, it cannot be a case of a garbled value or an out of range index -
> When in Windows or CWSDMPI -x mode the function always displays the correct
> label which it must, by definition, have pulled out from the array and
> therefore, the pointer must have contained a valid address or at least an
> address that can always be resolved correctly when in that mode.
The invalid address might be involved in some intermediate calculation
or test, so you might not see it directly in the results.
Trust us, we've seen more than enough such problems to know one when
we see it. Your best bet is running the program under a debugger, and
when it crashes, use the debugger's commands to see what's wrong with
the variables used in the line that crashed.
> I am off for a couple of days so it will not be until the Friday. Would you
> prefer me to post them on the newsgroup or send them as e-mail? I will only
> send a few lines (20 or so) as the entire program is of 4000 lines!
If it's only 20 lines or so, post it here. But please also post the
full crash message printed on DOS when your program crashes, and
please run SYMIFY on that crash message as section 9.3 of the FAQ
explains. This will make the responses much more efficient and
accurate.
> Your FAQ and prompt responses are invaluable - Thank you very much.
You are welcome.
- Raw text -