Actually, I think the present bug is the same as the newly reported https://bugs.launchpad.net/yade/+bug/1764753
Out of 4 FileGenerator, we have - two conforming the "new" (though years old) InteractionLoop definition, and that run: TriaxialTest and SimpleShear - two not conforming this definition but still directly including IGeom, IPhys, and Law2 classes directly in the engines list, and that segfault: CapillaryTriaxialTest and CohesiveTriaxialTest. And in these two buggy FileGenerators, crashs seem to occur in connection with IGeom operations.. Do we now agree to (try to ?) fix these FileGenerators with the new InteractionLoop definition, if not discarding them ? -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1625850 Title: CapillaryTriaxialTest preprocessor broken Status in Yade: Confirmed Bug description: Hi, When using either yadedaily or the latest (as of today) trunk version, CapillaryTriaxialTest preprocessor crashes at the first iteration. The backtrace obtained from a debug version of trunk is attached. I'm at the moment playing with capillary code before commit capillary scripts, but this crash happens with or without the "water" attribute of the preprocessor, ie with or without capillary Law2 in the engines, and with both yadedaily and trunk, so I do not think it's related. The crash occurs by the way during some IGeom operations, and the structure of O.engines defined by the preprocessor looks quite outdated (no InteractionLoop()). Anyway, I would happily hear from you that the same bug exists on other computers. Jerome To manage notifications about this bug go to: https://bugs.launchpad.net/yade/+bug/1625850/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
