yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #08674
Re: [Bug 803774] Re: Saving, loading simulation with erased bodies crash.
There is no need to post a script. You can (I can, at least) reproduce
the bug just by following instructions that were given below when the
bug was open. I think it is quite essential that we fix this as removing
bodies is a common operation. Can you please try to reproduce the bug
too, Anton (or anybody else) to make sure is not just me? Thanks, Chiara
On 2 Jul 2011, at 18:48, Anton Gladky wrote:
> Hopefully fixed in r2880.
> Please, check it. If the problem still appears, do not hesitate to reopen a bug.
>
> ** Changed in: yade
> Status: New => Fix Released
>
> ** Changed in: yade
> Importance: Undecided => Low
>
> --
> You received this bug notification because you are a member of Yade
> developers, which is the registrant for Yade.
> https://bugs.launchpad.net/bugs/803774
>
> Title:
> Saving, loading simulation with erased bodies crash.
>
> Status in Yet Another Dynamic Engine:
> Fix Released
>
> Bug description:
> Here is the bug :
>
> - launch yade (for example without any script)
> - add a sphere : O.bodies.append(utils.sphere((0.2,0.2,0.2),0.006))
> - delete it : O.bodies.erase(0)
> - save yade's universe : O.save("./test")
> - quit yade
> - launch yade
> - load the file : O.load("./test")
> ->segmentation fault
>
> I think it's because when you erase something the size of O.bodies (etc...) doesn't change and now contains an empty value. (the c++ array may not be dynamic ?)
> So when the O.load() function is called, yade try to load a non-existant body ?
>
> Maybe this can be fixed by changing the load() method ?
>
> I joined the debug output.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/yade/+bug/803774/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev
> Post to : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev
> More help : https://help.launchpad.net/ListHelp
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/803774
Title:
Saving, loading simulation with erased bodies crash.
Status in Yet Another Dynamic Engine:
Fix Released
Bug description:
Here is the bug :
- launch yade (for example without any script)
- add a sphere : O.bodies.append(utils.sphere((0.2,0.2,0.2),0.006))
- delete it : O.bodies.erase(0)
- save yade's universe : O.save("./test")
- quit yade
- launch yade
- load the file : O.load("./test")
->segmentation fault
I think it's because when you erase something the size of O.bodies (etc...) doesn't change and now contains an empty value. (the c++ array may not be dynamic ?)
So when the O.load() function is called, yade try to load a non-existant body ?
Maybe this can be fixed by changing the load() method ?
I joined the debug output.
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/803774/+subscriptions
References