> Generally no. If an assertion fails, that means something is wrong. > Ignoring the problem doesn't fix anything.
I can understand some of them. But Consider this assertion : assert(!load_inst->memData); load_inst->memData = new uint8_t[64]; Is it a must? On 12/7/11, Gabriel Michael Black <[email protected]> wrote: > Generally no. If an assertion fails, that means something is wrong. > Ignoring the problem doesn't fix anything. > > Gabe > > Quoting Mahmood Naderan <[email protected]>: > >> Hi, >> is it safe to convert assertions to "return" or "break". >> I don't know why this assertion >> >> assert(pkt->needsExclusive() && !blk->isWritable()); >> >> fails. So I want to changeit to this: >> >> if (!pkt->needsExclusive() && blk->isWritable()) >> break; >> >> Any idea? >> -- >> // Naderan *Mahmood; >> _______________________________________________ >> gem5-users mailing list >> [email protected] >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> > > > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > -- -- // Naderan *Mahmood; _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
