|
From: | Richard Shann |
Subject: | [Denemo-devel] [bug #36969] Yet Another Crash with 0.9.5rc2 Windows |
Date: | Wed, 15 Aug 2012 15:38:40 +0000 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-gb) AppleWebKit/531.2+ (KHTML, like Gecko) Version/5.0 Safari/531.2+ Debian/squeeze (2.30.6-1) Epiphany/2.30.6 |
Follow-up Comment #9, bug #36969 (project denemo): The debug output "loop" you see is generated by the script that checks the score for common errors before printing. The message (#f Wrong type to apply ...) is a message from a scheme script indicating that the script has an error in it. Errors in scripts should never cause an exit though as there is a trap handler set (which is what is generating that message). The "No of displays..." message is in the signal handler which is setup via signal (SIGSEGV, denemo_signal_handler); in main.c, it should mean that the program tried to access memory incorrectly. It is at this point that the program tries to save the file crashrecovery.denemo which may simply cause a further crash which will then exit. I guess you cannot reliably create this crash? Did they all involve the same file? _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?36969> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |