|Message: Re: double free or corruption (out) Issue||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
On Tue, 17 Dec 2013 19:28:40 GMT, Tom Roberts wrote:
> Using the Geant4 internal version of CLHEP fixed/avoided two problems: > 1. The crash while closing discussed in this thread. > 2. A build problem with CLHEP 126.96.36.199 on a supercomputer (apparently > CLHEP now has MPI code, which failed to compile). > > Remarkably, the Geant4 internal version of CLHEP has everything my > program needs; the version of Evaluator is recent enough to not have the > unary-minus bugs that plagued earlier versions. So I have removed my own > build of CLHEP from my Makefile-s, and am using the Geant4 internal > version.
In a sibling thread in this topic (http://hypernews.slac.stanford.edu/HyperNews/geant4/get/runmanage/362/2/1/1/1/1.html), Makoto noted that the original user's code had an uninitialized pointer which the dtor tried to delete (hence the "corruption" part of the error message). Is it possible that either your code, or the CLHEP class you were using, had a similar issue?
I've had a similar experience, where Linux will complain about exactly this problem, either at compile time (with -Wall) or at runtime (with a crash), but not my MacBook. I finally figured out that the Mac seems to have GCC configured to automatically initialize memory to zero, which masked this delete-uninitialized-pointer bug in my code.
-- Michael Kelsey
|Inline Depth:||Outline Depth:||Add message:|