maude-help AT lists.siebelschool.illinois.edu
Subject: Maude-help mailing list
List archive
- From: "Nishant Sinha" <ek.shaks AT gmail.com>
- To: maude-help AT peepal.cs.uiuc.edu, maude-bugs AT peepal.cs.uiuc.edu
- Subject: [Maude-help] debugging problems: out of memory, timeout facility
- Date: Fri, 19 Sep 2008 11:35:40 -0400
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=jqTldzoNpjHJ7Eht561Kcr7UMe97fH+JhPNIgJFHvgMgvExk1+amWdDmTCc1E6doUE lJudMvr2h5moKMw+/c9hVNZ0y8iUPRqjVziqiWH9KWqpoPU30qXjyZS2RBrve1569gqi OrJc8+Njrv/cW/Xgt37oYQh4BaxSgVgDscbFw=
- List-archive: <http://maude.cs.uiuc.edu/pipermail/maude-help>
- List-id: Maude help list <maude-help.maude.cs.uiuc.edu>
Hi,
I'm trying to debug a Maude (2.3) run using "set trace on" option.
Maude prints information about the rules being applied for some time,
but then it stops printing anything after a point and starts consuming
memory rapidly so that it crashes with a std::bad_alloc.
I'm quite sure that my rules are terminating - I've seen Maude keep
printing stuff if the rule set is non-terminating, so I think the
problem is somewhere else. In some cases, I've managed to avoid the
above behavior by commenting out some rules, but there is no
particular set of rules that I can pinpoint for different examples.
Also, is there a way to set a timeout for rewriting in Maude, i.e.,
Maude should be able to stop the current rewriting and output the
intermediate result if timeout occurs.
Please advice.
nishant
- [Maude-help] debugging problems: out of memory, timeout facility, Nishant Sinha, 09/19/2008
- [Maude-help] Re: debugging problems: out of memory, timeout facility, Steven Eker, 09/19/2008
Archive powered by MHonArc 2.6.16.