Open bsunanda opened 1 year ago
Hi @bsunanda , Can you provide a simple reproducer of your case? Together with some information about your system (how you installed ROOT etc., compiler version etc.)
Alternatively you can run valgrind
to get more information on this kind of failure:
valgrind --suppressions=$ROOTSYS/etc/valgrind-root.supp --log-file=val.01.log myexecutable myargs
Thanks Philippe - I shall try that
From: Philippe Canal @.*** Sent: 27 February 2023 18:50 To: root-project/root Cc: Sunanda Banerjee; Mention Subject: Re: [root-project/root] Getting a crash while reading a Root Tree (Issue #12370)
Alternatively you can run valgrind to get more information on this kind of failure:
valgrind --suppressions=$ROOTSYS/etc/valgrind-root.supp --log-file=val.01.log myexecutable myargs
— Reply to this email directly, view it on GitHubhttps://github.com/root-project/root/issues/12370#issuecomment-1446778005, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABGMZOSBSY5NDNIO7K6JZEDWZTSPBANCNFSM6AAAAAAVFHT3OU. You are receiving this because you were mentioned.Message ID: @.***>
Dear Philippe
Sorry for late response. The crash depends on the input file. I landed with one file and here is the log file which came from running valgrind. I cannot find out the real reason from this. Could you point out where I should look into this?? Thanks and regards
Sunanda
From: Sunanda Banerjee @.> Sent: 28 February 2023 14:10 To: root-project/root @.>; root-project/root @.> Cc: Mention @.> Subject: RE: [root-project/root] Getting a crash while reading a Root Tree (Issue #12370)
Thanks Philippe - I shall try that
From: Philippe Canal @.*** Sent: 27 February 2023 18:50 To: root-project/root Cc: Sunanda Banerjee; Mention Subject: Re: [root-project/root] Getting a crash while reading a Root Tree (Issue #12370)
Alternatively you can run valgrind to get more information on this kind of failure:
valgrind --suppressions=$ROOTSYS/etc/valgrind-root.supp --log-file=val.01.log myexecutable myargs
— Reply to this email directly, view it on GitHubhttps://github.com/root-project/root/issues/12370#issuecomment-1446778005, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABGMZOSBSY5NDNIO7K6JZEDWZTSPBANCNFSM6AAAAAAVFHT3OU. You are receiving this because you were mentioned.Message ID: @.***>
here is the log file which came from running valgrind
I don't find this; could you attach it at https://github.com/root-project/root/issues/12370 please?
The relevant part:
==9375== Conditional jump or move depends on uninitialised value(s)
==9375== at 0x44AFDA: CalibMonitor::correctEnergy(double&, long long const&) (in /afs/cern.ch/work/s/sunanda/public/CMSSW_12_4_6/relval/d22gm/CalibMain.exe)
==9375== by 0x4496BB: CalibMonitor::goodTrack(double&, double&, long long const&, bool) (in /afs/cern.ch/work/s/sunanda/public/CMSSW_12_4_6/relval/d22gm/CalibMain.exe)
==9375== by 0x4467E8: CalibMonitor::Loop(long long) (in /afs/cern.ch/work/s/sunanda/public/CMSSW_12_4_6/relval/d22gm/CalibMain.exe)
==9375== by 0x4664CA: main (in /afs/cern.ch/work/s/sunanda/public/CMSSW_12_4_6/relval/d22gm/CalibMain.exe)
==9375==
==9375== Invalid read of size 4
==9375== at 0x44B009: CalibMonitor::correctEnergy(double&, long long const&) (in /afs/cern.ch/work/s/sunanda/public/CMSSW_12_4_6/relval/d22gm/CalibMain.exe)
==9375== by 0x4496BB: CalibMonitor::goodTrack(double&, double&, long long const&, bool) (in /afs/cern.ch/work/s/sunanda/public/CMSSW_12_4_6/relval/d22gm/CalibMain.exe)
==9375== by 0x4467E8: CalibMonitor::Loop(long long) (in /afs/cern.ch/work/s/sunanda/public/CMSSW_12_4_6/relval/d22gm/CalibMain.exe)
==9375== by 0x4664CA: main (in /afs/cern.ch/work/s/sunanda/public/CMSSW_12_4_6/relval/d22gm/CalibMain.exe)
==9375== Address 0x0 is not stack'd, malloc'd or (recently) free'd
The crash depends on the input file. I landed with one file and here is the log file which came from running valgrind.
Does the crash with valgrind have the same symptoms as the original problem (i.e. seg fault in TStreamerInfoActions::VectorLooper::ReadCollectionBool
)?