Problem 451 - Ownership problem of G4VSensitiveDetectors
Summary: Ownership problem of G4VSensitiveDetectors
Status: CLOSED INVALID
Alias: None
Product: Geant4
Classification: Unclassified
Component: digits_hits (show other problems)
Version: 4.1
Hardware: PC Linux
: P1 normal
Assignee: Makoto.Asai
URL:
: 452 (view as problem list)
Depends on:
Blocks:
 
Reported: 2003-02-03 07:44 CET by alexander.brandt
Modified: 2012-02-15 09:55 CET (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this problem.
Description alexander.brandt 2003-02-03 07:44:41 CET 
In a prototype implementation we have "married" the G4VSensitiveDetector class
with a class from the Gaudi / Athena framework used at ATLAS software. Our
concrete sensitive detectors are as well G4VSensitiveDetectors (from G4
framework) as AlgTools (from Gaudi framework).

The problem is as follows: both, the G4RunManager as well as the ToolSvc (from
Gaudi) try to delete our concrete sensitive detectors (and lead to segfaults).

In fact, instead of deleting concrete sensitive detectors, the ToolSvc only
decreases a reference count. Undfortunately, the ToolSvc tries to release its
pointers after the G4RunManager already has deleted the corresponding objects.

It would be nice if G4VSensitiveDetectors itself would have such a reference
count system.

Best regards - Alexander Brandt
Comment 1 Makoto.Asai 2003-02-03 09:44:59 CET 
*** Bug 452 has been marked as a duplicate of this bug. ***
*** 'Makoto.Asai@cern.ch' will be responsible for bug 452. ***
Comment 2 Makoto.Asai 2003-02-03 09:46:59 CET 
Given the user want to use Gaudi framework, the user should have a
dedicated concrete implementation of G4RunManager.
Further discussions are welcome in HyperNews.