GSI Forum: Bugs, Fixes, Releases » segmentation violation in reco macro

Home » PANDA » PandaRoot » Bugs, Fixes, Releases » segmentation violation in reco macro

Show: Today's Messages :: Polls :: Message Navigator

Re: segmentation violation in reco macro -- GEANT related? [message #13618 is a reply to message #13617]

Fri, 15 June 2012 19:18

MartinJGaluska
Messages: 203
Registered: March 2010
Location: Germany

first-grade participant

From: *physik.uni-giessen.de

nEvents is set to 0.

I believed that represents "run until you reach the last event" (at least that is what fRun does when I call it with fRun->Run(0, nEvents); with nEvents set to 0).

Report message to a moderator

[Message index]

		segmentation violation in reco macro By: MartinJGaluska on Fri, 15 June 2012 13:11
		Re: segmentation violation in reco macro -- GEANT related? By: StefanoSpataro on Fri, 15 June 2012 13:38
		Re: segmentation violation in reco macro -- GEANT related? By: MartinJGaluska on Fri, 15 June 2012 13:44
		Re: segmentation violation in reco macro -- GEANT related? By: StefanoSpataro on Fri, 15 June 2012 14:06
		Re: segmentation violation in reco macro -- GEANT related? By: MartinJGaluska on Fri, 15 June 2012 18:37
		Re: segmentation violation in reco macro -- GEANT related? By: StefanoSpataro on Fri, 15 June 2012 18:52
		Re: segmentation violation in reco macro -- GEANT related? By: MartinJGaluska on Fri, 15 June 2012 19:18
		Re: segmentation violation in reco macro -- GEANT related? By: StefanoSpataro on Fri, 15 June 2012 20:27
		Re: segmentation violation in reco macro -- GEANT related? By: MartinJGaluska on Sun, 17 June 2012 15:09

Previous Topic:	Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMvdPix
Next Topic:	[FIXED] Possibly a bug in MC Truth Forwarding (?) - no bug after all [SOLVED]

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Sep 13 22:59:56 CEST 2024

Total time taken to generate the page: 0.00716 seconds