On 7/14/2022 8:07 PM, Abdlerhman Abotaleb wrote:
Thanks Eliot for the follow up.
The reposne is created independently using the memory controller.
and the problem arises inside recvTimingReq, so it happens even before complete
sending teh request.
I don't free up the pkt pointer "pkt", I pop the queue element, after the re-try manages to send the
packet.
and pop doesn't do any allocation free-up.
I think we're talking a little at cross purposes.
I was suggesting that some of the existing gem5
code was somehow freeing the packet, while you
had retained a pointer to it. So there's nothing
exactly wrong with your code in that scenario
except maybe having a wrong expectation about
the packet's lifetime.
EM
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
