Seg fault copying zero-event artroot file.
I get a seg fault from inside art when copying an artroot file with zero events.
$ lar -c copy.fcl -s /uboone/data/users/uboonepro/crash_zero.root
27-Nov-2017 17:06:36 CST Opened input file "/uboone/data/users/uboonepro/crash_zero.root"
%MSG-i FastCloning: RootOutput:out1@Construction 27-Nov-2017 17:06:36 CST ModuleConstruction
Initial fast cloning configuration (from default): true
27-Nov-2017 17:06:36 CST Opened output file with pattern "merged.root"
%MSG-w FastCloning: PostBeginSubRun 27-Nov-2017 17:06:36 CST run: 6551 subRun: 212
Fast cloning deactivated for this input file due to information in FileBlock.
The zero-event file was created with art v2.05.00. Crash happens with art v2_05.00 as well as art v2_08_04.
Crash happens in RootOutputFile.cc.
#0 0x00007ffff5433e2f in (anonymous namespace)::maybeInvalidateRangeSet (bt=art::InSubRun, principalRS=..., productRS=...) at /scratch/workspace/nu-release-build/v2_06_02/s43-e10/prof/build/art/v2_05_00/src/art/Framework/IO/Root/RootOutputFile.cc:227
The input file is not obviously corrupted, and was successfully written by art from an input file with a nonzero number of events.
#2 Updated by Kyle Knoepfel over 3 years ago
- Category set to Infrastructure
- Status changed from Accepted to Assigned
- Assignee set to Kyle Knoepfel
Herb, the problem is understood, and the solution is straightforward. Is it sufficient to issue a bug-fix release for
art 2.09? Or is a 2.08 bug-fix release required?
#5 Updated by Kyle Knoepfel over 3 years ago
- Status changed from Assigned to Resolved
- Target version set to 2.05.01
- % Done changed from 0 to 100
- Occurs In 2.05.00 added
- Occurs In deleted (
- SSI Package art added
Based on discussions with Herb, we will provide an
art 2.05 bug-fix release with the understanding that art series 2.06, 2.07, and 2.08 will not automatically include the fix. A bug-fix release from any of those series can be requested if necessary.