Hi Christoph, > To make it short, I was not able to reproduce any segfaults with my > compiled version 10.7.0 on my bullseye machine. I downloaded Geant4 > straight from the Cern Geant4 Gitlab, and used the same compilation > options I found in your debian/rules file (i.e. using the new option > GEANT4_USE_TBB=1 additionally). The examples I tried, as well as my own > old simulations, still work fine. I also replaced my RunManager with the > new task based RunManager, and that just lead to a huge amount of RAM > being used, but no segfault (it probably caches all events, and I have > to write a map/reduce function to process the results?). I have not yet > checked how the task-based approach is intended to be used, I just > confirmed that it doesn't segfault.
I'm really glad to hear that it didn't segfault for you! So I guess the issue then could be on my setup or my code. I'll try it again. > While looking into this, I stumbled upon this presentation: > https://indico.cern.ch/event/942142/contributions/4027521/attachments/2108316/3545985/G4Tasking-Status-and-Overview.pdf > (which is where I found out how to properly instantiate the different > RunManagers nowadays), which mentions on slide 10 something about the > program segfaulting when TBB is used and the G4RunManager is destroyed, > but that didn't happen in my tests, either. Thanks for sharing this. > I sadly have no clue how to use the files you put on salsa to build my > own package. I am merely a Debian user, not a developer or maintainer, > but I will look into it how to create a .deb package from those files > (probably dpkg-buildpackage?). If I succeed, I can give you more feedback. I'll give a (very quick) guide on how to build it. First you need the basic build utilities for building a .deb: build-essential debhelper devscripts Then clone https://salsa.debian.org/science-team/geant4 (tip: do this in an empty folder already for the output) To build the .deb, you simply run `debuild` (better in this case: `debuild --no-lintian --no-sign`). The final .deb is in the parent folder of the sources. Building might fail if you have build dependencies missing, they are listed in debian/control. Note that dh-sequence-python3 is provided by dh-python. Thanks and Regards, Stephan
