Hi Sir,
1. I have read the ExecutionState constructor and the constructors of all classes internally, I think everything is a deep copy. I suggest that you may read the source code with IDE so that you could find the implementation of some classes or functions quickly . 2. I'm not sure if there are some state share something with another. Regards, Chengyu -- 张枨宇 Chengyu Zhang 华东师范大学 计算机科学与软件工程学院 East China Normal University School of Computer Science and Software Engineering Mail：[email protected] At 2016-04-15 16:53:37, "Sumit Kumar" <[email protected]> wrote: Hi Chengyu, Thank you for the response. I have looked at the "branch" and "fork" function in Exector.cpp. Still I want to know the following: 1. When a new state is created in "fork" method by calling the ExecutionState constructor then does that constructor return a state that shares something with the old state or is everything a deep copy / new. I have looked at the ExecutionState constructor but it is difficult to figure out as it calls the constructor of many other classes internally. 2. Does at any other point in the whole program, one state is made to share something from other state. -- Thanks and Regards, Sumit On 15 April 2016 at 13:43, 张枨宇 <[email protected]> wrote: Sir, Maybe you could find the implement of forking state in lib/Core/ExecutionState.cpp with ExecutionState::branch() and ExecutionState::ExecutionState(const ExecutionState& state) functions. And ExecutionState::branch() is used in lib/Core/Executor.cpp Executor::fork(ExecutionState ¤t, ref<Expr> condition, bool isInternal) function when a state need to be forked. Regards, Chengyu -- 张枨宇 Chengyu Zhang 华东师范大学 计算机科学与软件工程学院 East China Normal University School of Computer Science and Software Engineering Mail：[email protected] At 2016-04-12 03:49:30, "Sumit Kumar" <[email protected]> wrote: Hi, Can anyone please tell me that when a state is forked does the newly created state share anything with its sibling or is everything a deep copy. -- Thanks and Regards, Sumit
_______________________________________________ klee-dev mailing list [email protected] https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
