From d4beb13c6d147fdeecab2d42bd5a91db5011885a Mon Sep 17 00:00:00 2001 From: Ben Webb Date: Thu, 21 Dec 2023 22:22:44 -0800 Subject: [PATCH] Update to IMP 2.20.0 --- doc/valgrind.ipynb | 4 ++-- support/tutorial_tools | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/valgrind.ipynb b/doc/valgrind.ipynb index 0fc18f6..3f6839c 100644 --- a/doc/valgrind.ipynb +++ b/doc/valgrind.ipynb @@ -61,7 +61,7 @@ "source": [ "# Build procedure\n", "\n", - "To build the custom module, either drop the entire module into IMP's `modules` directory and then build IMP from source code [in the usual way](https://integrativemodeling.org/2.19.0/doc/manual/installation.html#installation_compilation), or build the module [out of tree](https://integrativemodeling.org/2.19.0/doc/manual/outoftree.html) pointing CMake to an existing IMP installation. In order for Valgrind to be maximally useful, build the module with extra debugging information available by passing `-DCMAKE_CXX_FLAGS=\"-g\"` to CMake. The module should build without errors (or even warnings) with gcc." + "To build the custom module, either drop the entire module into IMP's `modules` directory and then build IMP from source code [in the usual way](https://integrativemodeling.org/2.20.0/doc/manual/installation.html#installation_compilation), or build the module [out of tree](https://integrativemodeling.org/2.20.0/doc/manual/outoftree.html) pointing CMake to an existing IMP installation. In order for Valgrind to be maximally useful, build the module with extra debugging information available by passing `-DCMAKE_CXX_FLAGS=\"-g\"` to CMake. The module should build without errors (or even warnings) with gcc." ] }, { @@ -145,7 +145,7 @@ " - In more complex programs with multiple code paths it can be tricky to make sure that every `new` is paired with a `delete` and that we never try to free the same memory more than once.\n", " \n", "\n", - "In this case where the object is small it would be better to avoid dynamic memory allocation entirely and just create the `ScoreCalculator` object as an automatic variable (on the stack) as `ScoreCalculator calc(d, k_);` For a larger object, derive from the [IMP::Object](https://integrativemodeling.org/2.19.0/doc/ref/classIMP_1_1Object.html) class and use a [smart pointer](https://en.wikipedia.org/wiki/Smart_pointer) to make sure it gets cleaned up automatically (replacing `new` with `IMP_NEW` and using `IMP::Pointer` rather than raw C++ pointers).\n", + "In this case where the object is small it would be better to avoid dynamic memory allocation entirely and just create the `ScoreCalculator` object as an automatic variable (on the stack) as `ScoreCalculator calc(d, k_);` For a larger object, derive from the [IMP::Object](https://integrativemodeling.org/2.20.0/doc/ref/classIMP_1_1Object.html) class and use a [smart pointer](https://en.wikipedia.org/wiki/Smart_pointer) to make sure it gets cleaned up automatically (replacing `new` with `IMP_NEW` and using `IMP::Pointer` rather than raw C++ pointers).\n", "\n", "(Valgrind also reports some small memory leaks from IMP's SWIG interface. These aren't worth worrying about, since this is not our code, and they should be one-time allocations, which get cleaned up at the end of the program anyway.)\n" ] diff --git a/support/tutorial_tools b/support/tutorial_tools index 4af36b2..077d2b3 160000 --- a/support/tutorial_tools +++ b/support/tutorial_tools @@ -1 +1 @@ -Subproject commit 4af36b2a72925f51c056ae2c7c60cfb98119cb75 +Subproject commit 077d2b3d7bf02c71fec866026f5e813393eb1f1d