Stack-overflow on assembly

[Phlippie Bosman]

Hi,

This is my first time using CILib. I have set up my environments correctly, I believe, but am getting stack overflows when running assembly on the project. From what I can tell, this is not a common problem, which leads me to suspect that the problem is with my system. I am using the following technologies:

ubuntu 10.04

javac 1.7.0_17

(I am using oracle's jdk, because openjdk is not available on ubuntu 10.04)

java version "1.7.0_17"

Java(TM) SE Runtime Environment (build 1.7.0_17-b02)

Java HotSpot(TM) Server VM (build 23.7-b01, mixed mode)

sbt 0.12.0 (as per project definition)

and the latest version of cilib as on today:

commit e3b7dd817a52c1ec24e90ed28aa3f28b2364d51a

Author: Gary Pamparà

Date:   Mon Mar 4 15:14:40 2013 +0200

    Merge of dmoo patch

Running compile and assembly leads to a stack overflow when parsing certain rules. I have pasted the output here.

Is anyone else getting this? Are my tools up to scratch? Can someone suggest another reason the project is acting this way?

Kind regards,

Phlippie

[Bennie Leonard]

Hi Phlippie,

The problem occurs because of the way that you specify the domain in your binaryQuantumPSO.xml file (all the xml files in the simulator/xml folder are constructed at compile time). If you remove your xml from that folder, compilation and assembly should work.

To fix your xml, however, you need to specify the domain correctly: "R(100:100)^d", where d is the dimensionality of the problem.

Hope this helps.

Regards,

Bennie Leonard

--
You received this message because you are subscribed to the Google Groups "cilib-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cilib-user+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Filipe Nepomuceno]

Hey,

If the domain is set up correctly another possible reason for the stack overflow is that java is running out of stack space. This can occur with high dimensional problems. To fix it just increase the stack space with -Xss2M or more if needed.

Regards,

Filipe

[Gary Pampara]

If you are still having issues, please can you provide a link to the xml?

[Phlippie Bosman]

Hi,

Thanks for the replies. Being new to all this, I didn't know what the files in simulator/xml were for. Am I correct in thinking that running assembly tests these files for validity?

The problem was with one of these files that "came with" CILib. Luckily, I'm not using these, so I could solve the problem by deleting all of them.

It's worth noting that the problematic file(s) came with my checkout of CILib. I will try and figure out which it is, and open an issue on github if there isn't one already.

Thanks for the help!

Regards,

Phlippie