Skip to Content.
Sympa Menu

maude-help - Re: [Maude-help] Debugging object modules written in Full Maude

maude-help AT lists.cs.illinois.edu

Subject: Maude-help mailing list

List archive

Re: [Maude-help] Debugging object modules written in Full Maude


Chronological Thread 
  • From: Pavel Strnad <pavel.strnad AT fel.cvut.cz>
  • To: "maude-help AT cs.uiuc.edu" <maude-help AT cs.uiuc.edu>
  • Subject: Re: [Maude-help] Debugging object modules written in Full Maude
  • Date: Sat, 30 Mar 2013 00:07:44 +0100
  • List-archive: <http://lists.cs.uiuc.edu/pipermail/maude-help/>
  • List-id: <maude-help.cs.uiuc.edu>

Thank you very much! I will try it.

Pavel

On 29. 3. 2013, at 23:25, Steven Eker
<eker AT csl.sri.com>
wrote:

> Where rewriting is occurring in multiple modules (say Full Maude, and at
> the metalevel, which is how Full Maude executes stuff) you can exclude
> rewrites from one for more given modules (such as Full Maude) from tracing
> so you only see the rewrites you are interested in. The command is:
>
> trace exclude <module names> .
>
> Steven
>
> On 3/29/13 11:48 AM, Pavel Strnad wrote:
>> Dear Maude users,
>> I am developing a specification of a concurrent object system using object
>> modules in Full Maude. I know how to debug and trace standard Maude
>> modules but the same approach does not work for Full Maude. Can you help
>> me please or target me to some literature?
>> Thanks in advance.
>> Regards
>> Pavel Strnad
>>
>>
>> _______________________________________________
>> Maude-help mailing list
>> Maude-help AT cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/maude-help
>
> _______________________________________________
> Maude-help mailing list
> Maude-help AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/maude-help






Archive powered by MHonArc 2.6.16.

Top of Page