Is something calling the curTick() method or are you saying that by virtue of wrapping curTick() it's being called somehow. I'm not sure how the latter could happen. In the case of the prior, any idea what's calling it?
Ali On 22.01.2013 14:56, Nilay wrote: > I am trying to allocate the main event queue(s) dynamically, but I am > running into a problem related to curTick(). In the file > src/python/swig/core.i, the function curTick() has been declared. This > leads SWIG to generate code that calls curTick(). It seems this function > call happens before the main event queue been allocated. Since the > function curTick() gets the tick value from the main event queue's tick > value, the call results in a segmentation fault. > > Can any one suggest some way out? > > -- > Nilay > > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev [1] Links: ------ [1] http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
