| From: | Alexander Niven-Jenkins |
| Date: | 28 Sep 2000 at 21:40:37 |
| Subject: | Re: How do I find this problem |
Hiya Jack,
On 28-Sep-00, you wrote:
> code within the program so I have no idea as to how to go about
> troubleshooting this problem. I have tried eliminating pieces of code but
> the error can be caused by just adding a function call like GoGetScreen()
> with the function GoGetScreen only containing a return statement. I can
> make the error go away by removing various statements, for the most part
> it doesn't seem to matter which ones. The program only uses about 3k of
> stack but I increased the shells stack to 20000 just to be safe. Does
> anyone have an idea on where to start with this? Is there a way
It's hard to say especially without hits attached :-)
I don't personally know where GoGetScreen() somes from I will assume
CyberGFX. I can only answer generally and at the time I was using HiSOFT
C++ although now I'm using StormC.
There is something wrong, well wrong is too strong a word, changed with
the amiga.lib that comes with the OS 2.1 dev CD, basically I found that
some of the functions (with HSC) would crash randomly unless I slowed down
the program, on changing to the exec.library equivalents all was well.
Could be a similar thing with StormC?
I did speak to Olaf at the time and he mentined something about creating
the linker library differently for the 2.1 release, as the functions had
exec.library equivalents, it didn't prove a problem.
Probably got nothing to do with it at all, but they were the exact
symtoms yu are suffering from, on removing random bits of code would solve
the problem, didn't mattr which.
Although the hits might say something else; although I can't see how they
don't point to your program? Do you mean the offsets? For these to work
properly you need to have all the debugging stuff on and to run the hits
through something like segtracker.
Kind regards...
Alex