Bug 1760 - Runtime bugs:Trying to allocate twice the same uid: ns3::RrFfMacScheduler
Runtime bugs:Trying to allocate twice the same uid: ns3::RrFfMacScheduler
Status: RESOLVED INVALID
Product: ns-3
Classification: Unclassified
Component: lte
ns-3.17
All All
: P5 normal
Assigned To: Nicola Baldo
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-10 22:34 UTC by Liu Haoyu
Modified: 2013-12-10 04:58 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Liu Haoyu 2013-09-10 22:34:51 UTC
Recently, I have some experiments to do with MBMS in LTE. But I haven't found open source code of MBMS and ns3 does not support MBMS. So I am trying to add the features of MBMS into the LTE module.

I write the code of MBMS mac scheduler which is in charge of allocating RBGs to MultiCast group UEs, make some changes in the other files of LTE module, and send data to UEs in a "for" loop.

After "Build successfully", there is a bug:
msg="Trying to allocate twice the same uid: ns3::RrFfMacScheduler", file=../src/core/model/type-id.cc, line=107
terminate called without an active exception
Command ['/home/lilalan/workspace/nsnam/build/scratch/lte-mbms'] terminated with signal SIGIOT. Run it under a debugger to get more information (./waf --run <program> --command-template="gdb --args %s <args>").

Then I debug the program and get this:
(gdb) run
Starting program: /home/lilalan/workspace/nsnam/build/scratch/lte-mbms \<args\>
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
msg="Trying to allocate twice the same uid: ns3::RrFfMacScheduler", file=../src/core/model/type-id.cc, line=107
terminate called without an active exception

Program received signal SIGABRT, Aborted.
0x00007fffefd39425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)

I don't know why this bug happens.
Please help.
Comment 1 Nicola Baldo 2013-12-10 04:58:33 UTC
Hi Liu,

the error you are reporting is not related with any ns-3 release, but rather just with your custom code. Hence this bug report is invalid. Messages of this kind should be posted to the ns-3-users mailing list instead.