[ndnSIM] Question about updating name prefix list of the routers

Junxiao Shi shijunxiao at email.arizona.edu
Sun Jun 11 11:50:41 PDT 2017

Hi Anil

The log indicates some code is calling ns3::NodeList::GetNode(-1), but -1
is obviously not a valid NodeId.
I guess this invalid NodeId comes from ns3::Simulator::GetContext(), which
usually returns the current NodeId on which an event is scheduled. However,
some code (most likely in main function or initialization procedure) has
scheduled an event without context, so that ns3::Simulator::GetContext() is
returning -1.
You may search for calls to ns3::Simulator::Schedule and replace them with
ns3::Simultor::ScheduleWithContext. The context value should indicate which
node the event should be happening.

Yours, Junxiao

On Jun 11, 2017 10:35, "Anil Jangam" <anilj.mailing at gmail.com> wrote:

Hi All,

Mahsa, Sabet, How have you solved this issue of SIGABRT?

I converted the "nlsrc" into a a ndn::Application instance and installed it
on each of the nodes. In my simulation example, I am scheduling a new
prefix injection (at 100.0 sec) from a node.

I see that experiment is running and at time 100 secs  into simulation, its
crashing. I am attaching the stack trace for more details. Can you help me
know what wrong here?

Let me know if you need additional info.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20170611/fe2bfbbf/attachment.html>

More information about the ndnSIM mailing list