Re: [Gems-users] TransactionVersionManager.C assertion failed

[Jayaram Bobba <bobba@xxxxxxxxxxx>]

m_maxLogSize is set in the beginning of a simulation when a thread calls 
set_transaction_registers() in
$GEMS/microbenchmarks/transactional/common/transaction.c
It passes the log base address and maximum log size to ruby via a magic 
call.
Jayaram

Jim Leek wrote:
> I keep getting this assertion failure:
>
> log_tm/TransactionVersionManager.C:208: bool 
> TransactionVersionManager::addLogEntry(int, int, Vector<uint32>&): 
> Assertion `m_logSize[thread] < (m_maxLogSize[thread] * 1024)' failed.
>
> I've tried a hundred different things, but it keeps coming back.  Does 
> anyone know what's causing it?  Can I set the m_maxLogSize bigger 
> somehow?  Please help.
> Jim
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>
>