Spinroot
A forum for Spin users
You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: General » p2b source code? » 2016-07-22 19:28:42
Thanks, I'll try tracking them down and asking.
p2b is referenced in a paper on your site: http://spinroot.com/spin/Workshops/ws01/baldamus.pdf
#2 General » p2b source code? » 2016-07-21 20:21:34
- Lholloway
- Replies: 2
During the defense of my PhD dissertation one of my professors had mentioned a tool called p2b that converted Promela code to code usable by SMV or nuSMV. However, it appears my Google-fu has failed me and I cannot find any trace of the source code only the papers that reference the location of where the source code once was. Does anyone have a pointer to the source code or a place I could find it? Thanks!
#3 Re: General » BFS_PAR Error when attempting to run pan » 2015-01-02 22:13:53
I got it to run, I had to set the value of kern.sysv.shmall to be the value of kern.sysv.shmmax / 4096.
As an example, if shmmax is 1GB (1073741824), shmall has to be 262144.
#4 Re: General » BFS_PAR Error when attempting to run pan » 2015-01-02 21:16:26
I created a very simple program that allocates shared memory using code found in pangen7.h and it allocated and released just fine until I attempted to allocate 32MB. When I did that, it could not allocate memory. It did however, have no problem allocating 16MB and lower.
I think it could be a configuration error on my end. 
#5 Re: General » BFS_PAR Error when attempting to run pan » 2015-01-02 05:23:39
When I run the command I get the following:
kern.sysv.shmmax: 1073741824
kern.sysv.shmmin: 1
kern.sysv.shmmni: 128
kern.sysv.shmseg: 32
kern.sysv.shmall: 4096
which should be ~1GB for shmmax.
#6 General » BFS_PAR Error when attempting to run pan » 2015-01-02 03:29:41
- Lholloway
- Replies: 7
I'm attempting to run pan using the multi-core breadth-first search on a Mac OS X Yosemite. I setup the shared memory as explained in the documentation; however, when I run pan I receive this error:
cpu00: no shared memory n=0
Does anyone have any pointers on how I should be going about debugging / attempting to fix the problem?
Thanks!
Pages: 1