[ndnSIM] An error when running scenario

[Sirapop Theeranantachai]

1. The error is different from yours.6-node bottleneck shows that you lack
some python module. The error is SIGSEGV which means segmentation fault (a
type of crash). Your code in scratch fails assertion check (not really a
crash).

2. In the example, you can either try without -visualize or try solving
module issue by installing kiwi and gnomedesktop

3. If not solved, try to see which line is causing segmentation fault by
eithrr using gdb (advanced) or printing out lines and see how far the code
goes.


On Wed, Apr 3, 2024, 4:01 AM 李怿曈 Yitong LI <yitongli at hkust-gz.edu.cn> wrote:

> Hi,
>
> I’ve regenerated the error from online example “6-node bottleneck
> topology” (
> https://ndnsim.net/current/examples.html#node-bottleneck-topology). When
> I run it using “./waf —run xxx —visualize”, then click simulate button in
> the graphic interface, it will automatically exit and give errors below in
> one second.
>
> *caster at ubuntu:~/ndnSim/ns-3$ ./waf --run test-bottleneck --visualize*
> *Waf: Entering directory `/home/caster/ndnSim/ns-3/build'*
> *Waf: Leaving directory `/home/caster/ndnSim/ns-3/build'*
> *Build commands will be stored in build/compile_commands.json*
> *'build' finished successfully (1.930s)*
> *Could not load plugin 'show_last_packets.py': No module named 'kiwi.ui'*
> *Could not load icon applets-screenshooter due to missing gnomedesktop
> Python module*
> *scanning topology: 6 nodes...*
> *scanning topology: calling graphviz layout*
> *scanning topology: all done.*
> *Command ['/home/caster/ndnSim/ns-3/build/scratch/test-bottleneck',
> '--SimulatorImplementationType=ns3::VisualSimulatorImpl'] terminated with
> signal SIGSEGV. Run it under a debugger to get more information (./waf
> --run <program> --gdb").*
>
> Except for the error reason for this example, I’ll appreciate it very much
> if you can give me some guidance on how to find out the problem when
> running scenarios, as the errors normally don’t indicate where are they
> occur.
>
> Many thanks,
> Caster
>
> 2024年4月3日 下午5:30，Sirapop Theeranantachai <sirapop741 at gmail.com> 写道：
>
>  It appears that your code may have issue with
> ns3::RandomRectanglePositionAllocator.
> Which specific online example did you use, and are you sure it gives you
> exactly the same error? Would be great if you could provide the error
> message from the official documentation.
>
> On Wed, Apr 3, 2024, 1:26 AM 李怿曈 Yitong LI <yitongli at hkust-gz.edu.cn>
> wrote:
>
>> Hi all,
>>
>> I’ve installed ndnSIM and tested it using example code. But when I tried
>> to run some example codes from the online documentation and my own
>> scenarios, it will appears the same error. For some programs, it will
>> appear immediately when executing them, some other programs will show this
>> error after visualization module is loaded and run for a few seconds. I’ve
>> attached the log below and my source code. I appreciate your help!
>>
>> *caster at ubuntu:~/ndnSim/ns-3$ ./waf --run ndn-random --visualize*
>> *Waf: Entering directory `/home/caster/ndnSim/ns-3/build'*
>> *Waf: Leaving directory `/home/caster/ndnSim/ns-3/build'*
>> *Build commands will be stored in build/compile_commands.json*
>> *'build' finished successfully (3.593s)*
>> *assert failed. cond="uid != 0", msg="Assert in TypeId::LookupByName:
>> 0:100 not found", +0.000000000s -1 file=../src/core/model/type-id.cc,
>> line=834*
>> *terminate called without an active exception*
>> *Command ['/home/caster/ndnSim/ns-3/build/scratch/ndn-random',
>> '--SimulatorImplementationType=ns3::VisualSimulatorImpl'] terminated with
>> signal SIGIOT. Run it under a debugger to get more information (./waf --run
>> <program> --gdb”).*
>> Thanks,
>> Caster
>> _______________________________________________
>> ndnSIM mailing list
>> ndnSIM at lists.cs.ucla.edu
>> https://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20240403/5bdbf724/attachment-0001.htm>