← Back to team overview

yade-users team mailing list archive

Re: [Question #152794]: compiled YADE ?!

 

Question #152794 on Yade changed:
https://answers.launchpad.net/yade/+question/152794

Anton Gladky proposed the following answer:
I am almost completely sure, that the problem is in VMware.
I heard, that there were some problems with 3D-support, that is why,
perhaps, yade crashes.

You can try VirtualBox, It has better 3D-support .

Anton



On Fri, Apr 15, 2011 at 9:17 AM, Christian Jakob
<question152794@xxxxxxxxxxxxxxxxxxxxx> wrote:
> Question #152794 on Yade changed:
> https://answers.launchpad.net/yade/+question/152794
>
> Christian Jakob posted a new comment:
> Ok, Anton gave me the hint, that the problem has something to do with my VMware.
> My host system is Windows XP and I created a virtual machine with VMware player 3.1.4.
> Maybe there is a problem with graphics and the glutInit function, as you assumed.
> I will compile without qt4 support and post the results in the next message.
>
> [me@localhost ~]$ yade --debug --test
> Math: Matrix3 operations ... ok
> Math: Quaternion operations ... ok
> Math: Vector2 operations ... ok
> Math: Vector3 operations ... ok
> Core: correct types are instantiated ... ok
> Core: dispatcher ctors with functors ... ok
> Core: Attr::hidden ... ok
> Core: InteractionLoop special ctor ... ok
> Core: invalid attribute access raises AttributeError ... ok
> Core: Attr::noSave ... ok
> Core: ParallelEngine special ctor ... ok
> Core: class ctor's attributes ... ok
> Core: Attr::triggerPostLoad ... ok
> Core: dispatcher and functor type mismatch is detected ... ok
> Bodies: erased bodies are None in python ... ok
> Bodies: Iterator silently skips erased ones ... ok
> Bodies: Iteration ... ok
> Bodies: len(O.bodies) ... ok
> Bodies: Negative index counts backwards (like python sequences). ... ok
> I/O: All classes can be saved and loaded with boost::serialization ... WARNING: cannot open files used for capillary law, all forces will be null. Instructions on how to download and install them is found here : https://yade-dem.org/wiki/CapillaryTriaxialTest.
> ok
> Loop: dead engines are not run ... ok
> Loop: O.engines can be modified inside the loop transparently. ... ok
> Loop: substepping ... ok
> Material+State: CpmMat returns CpmState when asked for newAssocState ... ok
> Material+State: throws when body has material and state that don't work together. ... ok
> Material+State: throws when body has material but NULL state. ... ok
> Material: find by index or label; KeyError raised for invalid label. ... ok
> Material: iteration over O.materials ... ok
> Material: len(O.materials) ... ok
> Material: negative index counts backwards. ... ok
> Material: shared_ptr's makes change in material immediate everywhere ... ok
> Material: shared_ptr's are preserved when saving/loading ... ok
> PBC: degenerate cell raises exception ... ok
> PBC: homothetic cell deformation adjusts particle position (homoDeform==1) ... ok
> PBC: homothetic cell deformation adjusts particle velocity (homoDeform==3) ... ok
> PBC: utils.kineticEnergy considers only fluctuation velocity, not the velocity gradient (homoDeform==3) ... ok
> PBC: utils.kineticEnergy considers only fluctuation velocity, not the velocity gradient (homoDeform==1) ... ok
> PBC: L3Geom computes incident velocity correctly (homoDeform==3) ... ok
> PBC: L3Geom computes incident velocity correctly (homoDeform==1) ... ok
> PBC: ScGeom computes incident velocity correctly (homoDeform==3) ... ok
> PBC: ScGeom computes incident velocity correctly (homoDeform==1) ... ok
> PBC: setBox modifies hSize correctly ... ok
> PBC: chaing trsf changes hSize0, but does not modify hSize ... ok
> PBC: velGrad changes hSize but not hSize0, accumulates in trsf ... ok
> Clump: ids and flags consistency ... ok
> Clump: mass, centroid, intertia ... ok
> Clump: velocities of member assigned by NewtonIntegrator ... ok
> CohesiveChain: velocity/positions tested in transient dynamics and equilibrium state ... ok
> Doctest: yade.eudoxos.IntrSmooth3d ... ok
> Doctest: yade.pack.SpherePack_toSimulation ... ok
> Doctest: yade.plot.addAutoData ... ok
> Doctest: yade.plot.addData ... ok
> Doctest: yade.plot.plot ... ok
> Doctest: yade.plot.saveDataTxt ... ok
> Doctest: yade.utils.SpherePWaveTimeStep ... ok
> Doctest: yade.utils.saveVars ... /home/me/YADE/lib/yade-bzr2811/dbg/py/yade/utils.py:55: UserWarning: Overwriting yade.params.something which already exists.
>  if mark in yade.params.__dict__: warnings.warn('Overwriting yade.params.%s which already exists.'%mark)
> ok
> Doctest: yade.utils.sphere ... ok
> Doctest: yade.utils.typedEngine ... ok
>
> ----------------------------------------------------------------------
> Ran 58 tests in 8.772s
>
> OK
> *** ALL TESTS PASSED ***
>
>
> [me@localhost ~]$ yade --debug --check
> Welcome to Yade bzr2811 (debug build)
> ###################################
> running:  checkTestTriax.py
> WARN  py/log.cpp:49 logSetLevel: Yade was compiled without log4cxx support. Setting log levels from python will have no effect (warn once).
> Status: success
> ___________________________________
> ###################################
> running:  checkWeight.py
> Precalculated weight 4536.560323
> Obtained weight 4536.560323
> Status: success
> ___________________________________
> ###################################
> running:  checkTestDummy.py
> checkTest mechanism
> Status: success
> ___________________________________
>
>
> [me@localhost ~]$ yade
> Welcome to Yade bzr2811
> TCP python prompt on localhost:9000, auth cookie `kudyse'
> XMLRPC info provider on http://localhost:21000
> Segmentation fault
> [me@localhost ~]$
>
> --
> You received this question notification because you are a member of
> yade-users, which is an answer contact for Yade.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-users
> Post to     : yade-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-users
> More help   : https://help.launchpad.net/ListHelp
>

-- 
You received this question notification because you are a member of
yade-users, which is an answer contact for Yade.