|Message: Double delete in G4CrossSectionDataSetRegistry?||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 a simulation that I run, the simulation doesn't necessarily end cleanly, with a bunch of malloc errors reported. This is after the simulation has completed running, and the program is trying to clean up after itself (i.e., after EndOfRunAction has been called). Here is a transcript of the messages from the Idle> prompt:
Idle> exitOne of my colleagues may have traced the malloc errors down to the G4CrossSectionDataSetRegistry::Clean() method. He has found that simply by commenting out line 71, "delete xSections[i];", the malloc errors go away.
Could it be possible that the entries in the xSections vector are being deleted elsewhere? Perhaps G4CrossSectionDataSetRegistry::Clean() or DeRegister() is called from somewhere else, and then when the class is destroyed Clean() is called again?
On a related note, I'm curious as to why the entries within the xSections vector is set to 0 within this class, rather than calling xSections.erase().
Thanks for any comments.
|Inline Depth:||Outline Depth:||Add message:|