|Message: Re: Memory Overwrite||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Hi Chibueze, this is not the correct forum for discussing generic debug issues. Unless you're effectively running out of memory, or having any system related problem, given the statistics you're trying to run in a single run... a possibility for you to further investigate your problem is to use the Valgrind tool in conjunction with a debug build of your libraries and application, eventually storing seeds and restarting from the faulty event. You may be lucky and reproduce the error in a reasonable time. Gabriele ----------------- On Mon, 16 Feb 2009 10:30:25 GMT, Chibueze Zimuzo wrote: > Hi all, > > I encountered an error that looks like memory overwirte when large > number of events (see below) were ran. I needed to run about 500 million > events to generate some good statistics for my analysis . Tracing the > bug has been difficult as the command: (gdb) bt is constantly returning > no stack. > > Can anyone please give some practical hints how I can tackle the > problem? > > Thanks. > > Chibueze. > > Event: 21982379 > Event: 21982380 > terminate called after throwing an instance of 'std::bad_alloc' > what(): St9bad_alloc > Aborted > czu1@tesla:~/GATE/geant4.8.1. > p02/CC/CC_Series2/CC_Test3$