riebl / artery

OMNeT++ V2X simulation framework for ETSI ITS-G5
GNU General Public License v2.0
203 stars 129 forks source link

Runtime error on run_example #233

Closed khevessy closed 2 years ago

khevessy commented 2 years ago

Hello,

I built without any error. Now I have the same problem as in #52: when I try to run cmake --build build --target run_example, I get the following error:

A runtime error occurred:

Class "VeinsConnectionManager" not found -- perhaps its code was not linked
in, or the class wasn't registered with Register_Class(), or in the case of
modules and channels, with Define_Module()/Define_Channel() -- in module
(omnetpp::cModule) World (id=1), during network setup

Launch a debugger with the following command?

nemiver --attach=46371 &

I tried recompiling but with no success. I also tried reinstalling python3.

My setup: Linux Mint 20 (Ubuntu 20.04). Omnet++ 5.7 cmake 3.16.3 make 4.2.1 gcc 9.3.0 boost 1.71.0

Do you have any idea what could I be doing wrong?

Regards, Karel

riebl commented 2 years ago

Hi Karel,

are there any further (error) messages printed before "A runtime error occurred"?

Regards, Raphael

khevessy commented 2 years ago

Hi Raphael,

no, there are not any errors before. After I press Just break in that error window, make stack trace is shown in a command line:

Trace/breakpoint trap (core dumped)
make[3]: *** [scenarios/artery/CMakeFiles/run_example.dir/build.make:57: scenarios/artery/CMakeFiles/run_example] Error 133
make[2]: *** [CMakeFiles/Makefile2:1380: scenarios/artery/CMakeFiles/run_example.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:1387: scenarios/artery/CMakeFiles/run_example.dir/rule] Error 2
make: *** [Makefile:513: run_example] Error 2

By the way, what I want to accomplish in the end is running your Vanetza stack on a V2X device and then decide if I will be writing my own implementation of C-ITS protocols. So running Artery in a Linux PC is just a preparatory step for me to get started with this and if it is not possible to run this example for me, it is not such a big deal.

Regards, Karel

riebl commented 2 years ago

I have just installed OMNeT++ 5.7 to check if this triggers some errors on my machine. However, everything builds and runs smoothly here. The versions of your listed packages look also fine to me.

Can you please directly invoke make run_example in your build directory? I think cmake may hide some output.

khevessy commented 2 years ago

Hi,

I tried it but unfortunately, the error output is still the same. Here is whole console output for you:

[ 51%] Built target INET
[ 52%] Built target traci
[ 57%] Built target veins
[ 57%] Built target common
[ 57%] Built target net
[ 58%] Built target access
[ 62%] Built target asn1_support
[ 74%] Built target asn1_its
[ 74%] Built target asn1
[ 82%] Built target asn1_pki
[ 87%] Built target asn1_security
[ 89%] Built target security
[ 90%] Built target dcc
[ 92%] Built target geonet
[ 92%] Built target btp
[ 92%] Built target facilities
[ 92%] Built target gnss
[ 97%] Built target core
[ 98%] Built target envmod
[100%] Built target storyboard
OMNeT++ Discrete Event Simulation  (C) 1992-2021 Andras Varga, OpenSim Ltd.
Version: 5.7, build: 211004-1d27e5f35e, edition: Academic Public License -- NOT FOR COMMERCIAL USE
See the license for distribution terms and warranty disclaimer

Setting up Qtenv...

Loading NED files from /home/karosa/work/stack/pokus2/artery/src/artery:  113
Loading NED files from /home/karosa/work/stack/pokus2/artery/src/traci:  21
Loading NED files from /home/karosa/work/stack/pokus2/artery/extern/veins/examples/veins:  1
Loading NED files from /home/karosa/work/stack/pokus2/artery/extern/veins/src/veins:  43
Loading NED files from /home/karosa/work/stack/pokus2/artery/extern/inet/src:  670
Loading NED files from /home/karosa/work/stack/pokus2/artery/extern/inet/examples:  175
Loading NED files from /home/karosa/work/stack/pokus2/artery/extern/inet/tutorials:  19
Loading NED files from /home/karosa/work/stack/pokus2/artery/extern/inet/showcases:  33

Loading images from './bitmaps': *: 0 
Loading images from './images': *: 0 
Loading images from '/media/karosa/Windows/Users/Karosa/Documents/work/stack/omnetpp-5.7/images': *: 0  abstract/*: 90  background/*: 4  block/*: 320  device/*: 195  logo/*: 1  maps/*: 9  misc/*: 70  msg/*: 55  old/*: 111  status/*: 28 

qt5ct: using qt5ct plugin
qt5ct: D-Bus global menu: no
Trace/breakpoint trap (core dumped)
make[3]: *** [scenarios/artery/CMakeFiles/run_example.dir/build.make:57: scenarios/artery/CMakeFiles/run_example] Error 133
make[2]: *** [CMakeFiles/Makefile2:1380: scenarios/artery/CMakeFiles/run_example.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:1387: scenarios/artery/CMakeFiles/run_example.dir/rule] Error 2
make: *** [Makefile:513: run_example] Error 2

Thanks, Karel

riebl commented 2 years ago

Hm, that is strange. Do you see an output line with -- Enable Veins integration when you invoke cmake . in your build directory? You should see several such feature integration lines in the form of --Enable \<feature> integration along with Veins.

khevessy commented 2 years ago

Yes, I can see that, whole output for cmake . is:

-- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake (found suitable version "1.71.0", minimum required is "1.59") found components: date_time system 
-- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake (found suitable version "1.71.0", minimum required is "1.58") found components: date_time 
-- GeographicLib: using lookup code by Vanetza
-- SimuLTE integration disabled
-- Enable Veins integration
-- Enable INET integration
-- Configuring done
-- Generating done
-- Build files have been written to: /home/karosa/work/stack/pokus2/artery/build
khevessy commented 2 years ago

Do you think that the problem might be caused by the fact that I have installed Omnet++ without Akaroa, is it needed?

khevessy commented 2 years ago

Hello Raphael,

I tried the build process again on freshly installed Linux Mint and it can now be run okay. I do not know what was wrong, on the old system the problem persists. I think we can now close the issue. Thank you for your kind help.

Regards, Karel