Chris Condrat on Sun, 23 Oct 2005 07:04:02 +0200
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
Lifting and handling errors
- To: email@example.com
- Subject: Lifting and handling errors
- From: Chris Condrat <firstname.lastname@example.org>
- Date: Sat, 22 Oct 2005 23:02:16 -0600
- Delivery-date: Sun, 23 Oct 2005 07:04:02 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=fD1F96OWP7IYV7AGwGCMyLW+53Z9NqQ5Y6XPWmd2TX8vEFUixn7aRi6/qOfuprUTTliZDQpYtUAvwK/0LrBrHlUsF6MH/aIvjf8ESBuANcoImi0C4OrvcnICX7z0VC2vtezszYPGCcWh6fjemdiFbTRzNowHfJSG6kUsP7ddLyQ=
- Mailing-list: contact email@example.com; run by ezmlm
I'm coding a program that generates a very long multivariate polynomial with a great number of polynomial and integer modulo operations. The program, and amount of data fed to it, is such that I expect that the stack will overflow, in fact that's part of the design--a sort of work-as-far-as-you-can design. When a stack-overflow is encountered, I'd like to be able to dump out the polynomial before the stack-overflow-causing operation, as is, to a text file, so I can feed it to a different program. I'd also like to be able to apply lift() operations to the polynomial to "clean it up" before it is dumped, but I'm afraid that because of the stack overflow, there may not be enough room to complete that operation without another stack-overflow.
Any hints on how these tasks could be accomplished would be appreciated. Thank you.