Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!hplabs!otter.hpl.hp.com!hpltoad!cdollin!kers From: kers@hplb.hpl.hp.com (Chris Dollin) Newsgroups: comp.sys.acorn Subject: No stack for trap handler Message-ID: Date: 11 Feb 91 08:46:37 GMT Sender: news@hplb.hpl.hp.com (Usenet News Administrator) Distribution: comp Organization: Hewlett-Packard Laboratories, Bristol, UK. Lines: 27 Nntp-Posting-Host: cdollin.hpl.hp.com I am getting fairly often the message "No stack for trap handler" (followed by a PC etc value) from a C program I have written; the program is then terminated. This is a bummer, because I have no real clue as to what is going wrong. (a) What soes the message *mean* (ie, *why* is there no stack for the trap handler, and how can I find out where it was and what the unhandled trap was)? (b) Any likely candidates for errors? (It's not malloc failure, and I don't think it's realloc failure, but it *could* be writing out of bounds; however, the same code seems to run OK on my HP-UX workstation). (c) The error is more likely to occur running with the ARM3 cache on, and less likely to occur outside the desktop (ie, CTRL/SHIFT/F12 rather than F12 or a task window). I have an A440 (old style) with a recent ARM3 upgrade. (Yes, I do suspect the upgrade, but the same error happened on my wife's A440/2+2Mb (if that's the right designation)). Since I presently have run-times up to 16 hours, aborting part-way through is distinctly painful! -- Regards, Kers 24059 | "You're better off not dreaming of the things to come; Caravan: | Dreams are always ending far too soon."