Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gnb aborted (core dumped) #241

Closed
s5uishida opened this issue Oct 8, 2023 · 4 comments
Closed

gnb aborted (core dumped) #241

s5uishida opened this issue Oct 8, 2023 · 4 comments
Assignees

Comments

@s5uishida
Copy link

s5uishida commented Oct 8, 2023

Issue Description

When build the latest main branch on Ubuntu 22.04 (Virtualbox VM) and run gnb, it aborted.

Setup Details

# cd ~/srsRAN_Project
# mkdir build
# cd build
# cmake ../ -DENABLE_EXPORT=ON -DENABLE_ZEROMQ=ON -DAUTO_DETECT_ISA=OFF
# make -j`nproc`

Expected Behavior

gnb should work without abnormal termination.

Actual Behaviour

# cd ~/srsRAN_Project/build/apps/gnb
# ./gnb
/root/srsRAN_Project/include/srsran/adt/interval.h:53: constexpr srsran::interval<T, RightClosed>::interval(U, V) [with U = int; V = unsigned int; T = unsigned int; bool RightClosed = true]: 
Assertion `start_ <= stop_' failed - Invalid interval [2, 1).
Aborted (core dumped)

Steps to reproduce the problem

Additional Information

@AlaiaL
Copy link
Contributor

AlaiaL commented Oct 10, 2023

Hi Shigeru,

while I am trying to reproduce it locally would you be able to rebuild it in debug and run it again?
You can do it with this cmake command:
cmake ../ -DENABLE_EXPORT=ON -DENABLE_ZEROMQ=ON -DAUTO_DETECT_ISA=OFF -DCMAKE_BUILD_TYPE=Debug

Then the gNB would produce a backtrace and you can share it here.

Regards.

@s5uishida
Copy link
Author

Hi @AlaiaL

I created a new Virtualbox VM and tried again, and it worked fine both with and without the cmake debug option.
I do apologize for any inconvenience caused.

@s5uishida
Copy link
Author

Hi @AlaiaL

I got the cause.

When the number of CPU cores in the VM was 1, an error occurred at starting gnb, but when the number of CPU cores in the VM was 2 or more, the error did not occur and it worked.

Previously, it worked even with 1 core, but that seems to have changed recently.

@AlaiaL
Copy link
Contributor

AlaiaL commented Oct 11, 2023

Hi @s5uishida,

Thanks for the info. I will look at it.

Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants