-
Notifications
You must be signed in to change notification settings - Fork 132
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
TraCIAPI: segfault when subscribing simulation variables [was: Artery debug mode error] #62
Comments
Hi @brianmc95, I see no error in your posted stack trace. Which kind of error are you referring to? |
Hi @riebl The error I get a Segmentation Fault the gdb error I get is below
The error comes from the TraciAPI::readVariables function in TraciAPI.cc to send you a snippet where the error occurs it's below.
There's another stack trace below but might not be terribly useful.
Thanks for getting back to me at the same time much appreciated, let me know if you need me to try running anything else that might be of some help figuring this out. |
@brianmc95 Please check the updated master branch including a bugfix for |
@riebl Unfortunately after a fresh clone and setup, still the same issue as before. |
Hm, it's quite hard for me to investigate this issue further because I am not suffering from segmentation faults in debug mode. However, the line you have posted clearly shows an invalid pointer with You may set a breakpoint at |
So on looking through it, it appears the |
Actually, all the code under Often the output by Valgrind is also helpful to track down bugs. You can run a scenario with Valgrind via Edit: Oops, for |
Ah I hadn't thought that it was a sumo issue but you are probably right, in which case apologies for putting it in your repo. But thanks for letting me know how to run Valgrind and for all the help, I really appreciate it. I'll attach the output of the valgrind run below in case it's of interest, don't feel obliged to go through it.
I realise there's a newer version of sumo available, 1.1.0 while I'm on 1.0.1 I may just upgrade to that and see if the issue persists and possibly try one of the older versions as well. I'll update this issue with anything I find out just in case someone else stumbles across this. If as I feel it is a SUMO issue and it persists in 1.1.0 I'll raise the issue there and link to it from here. Thanks so much for the help again, I'll close this issue once I have gone through the above and confirmed it's SUMO. |
Minor update, tried again with all available version 1 sumo setups so SUMO |
@brianmc95 Any update on this issue? |
I ended up sidetracked with other issues. But I spent some time in the last 2 days and did a full new setup of OMNeT++ / SUMO / artery on Ubuntu (I had it running on a debian VM). But on some initial runs I can see that it's now working, so it must have been some sort of issue with Debian that was causing it. Going to close the issue as I don't think it's worth investigating the cause on Debian. |
Hello, I have run into a strange issue with running artery in debug mode. It seems that there is some issue with the setup of the scenarios in debug mode which causes an error to occur when running any
debug simulation.
I am running Omnet++ 5.4.1 with SUMO 1.0.1, gdb 7.12-6, running on Debian 9
The following is what I'm running the basic debug example
Below is a backtrace of what issue happens when beginning a simulation in debug mode.
Is there any obvious issue that would cause this, I can't determine what the cause might be, especially as if I run the example in release mode it works normally. This also happens with all other scenarios, and same applies, debug doesn't work, while release does. Any clues, it may be due to my own setup that's causing the issue as well I can't be sure.
The text was updated successfully, but these errors were encountered: