-
Notifications
You must be signed in to change notification settings - Fork 492
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
Cannot use Debug mode in INET anymore #982
Comments
make sure that you |
Sadly that didn't work. Then performed the following steps:
Then I again imported the INET project using the "Open projects from file system" menu and tried to run a simulation in debug mode. |
Some additional information:
Getting the same two errors and no clue what else to try. I think the problem occurs since I moved from Ubuntu 22.04 to 24.04. |
It's strange as the file reporting the error (gdbinit.py) is in OMNeT++ and does not reference any inet specific package so I don't know why it throws an exeception. I will try to reproduce this. I recently upgraded to ubuntu 24.04, too. |
Try starting the python repl and |
I'm currently setting up a Ubuntu 24.04 VM and I will try to reproduce the issue there.
|
Hmmm. Besides, the following packages are used by the inet module: @levy I'm not sure why the debugger's init script wants to import the inet module at all. This prevents debugging if the above modules are not present in the actual python virtual environment. |
Even when the file is present inet tries to load it from [workspace]/inet/.nedexclusions even though the automatic install installs inet in [workspace]/inet4.5 I created a new workspace and pulled the inet 4.5.2 tag manually into [workspace]/inet Also for debugging i still get the same error. My Ubuntu 24.04 VM is still setting up. |
More detailed: Within omnet I can rightclick the inet folder and click on "Show in local terminal" i can do the following:
However, if I click on the "Open console" in the bottom part and then on "PyDev console" i get the following error:
So for some reason it feels like I am in the correct environment in one case but I'm not on the other. Also the PYTHONPATH is different in both cases.
Second case:
|
So I was able to recreate this issue in a clean Ubuntu 24.04 VM. I can export the VM and provide the VM image if that helps. Steps to reproduce: 2: Install all packages as stated in the OMNeT++ installation guide:
This will fail as it libwebkit2gtk-4.0-37 is not found, so I installed everything else 3: Install python modules:
So instead install them with apt-get:
posix_ipc does not exist here so in installed that using
4: Downlad and setup omnetpp:
5: Start omnetpp from console
6: Create an empty workspace ( 7: Install inet 8: Import the inet folder in OMNeT++ in your workspace |
And here the .log file from [workspace]/.metadata/.log: |
Normally the debugger should not depend on optional packages, but it seems it is not the case. It is definitely a bug. As a workaround try to install the following packages in the virtual env: dask distributed py4j ipython optimparallel sewar |
Sadly even then I cannot use the debug mode.
I completely deleted the workspace and reperformed steps 5 to 8 above Checked that everything is set up correctly:
Which worked just fine When repeating step 9 I still get the same error. |
Another interseting thing, when I try to recreate the issue manually
Everything works just fine. If I click the debug button in OMNeT++ now I again get this error:
If I now perform the same steps as above again and excute the gdbinit manually, the output differs:
This is due to a file
// Edit: I'm still really curious why I did not have this problem on my earlier Kubuntu 22.04 though. |
Thanks for writing a detailed bug report! We will get back to you seen when @rhornig is back in the office. |
Hello, I'm running arch linux and figured out, that I can switch between a working version and a version with this issue by updating/downgrading the I used the following commands to update/downgrade According to https://www.sourceware.org/gdb/news/ and https://ftp.gnu.org/gnu/gdb/ there are no |
I just checked and my the version on my system seems to be 15.0.50.20240403-0ubuntu |
Other non GDB related inet and omnetpp python packages are not imported anymore.
Please note that the FIX is not yet taken-over to the master branch. It is fixed only in the 4.5.x branch. |
Accoring to what is shown on this page (top left), the commit seems to be part of the master branch already: |
indeed. (I forgot to fetch from the repo before checking this). A tip: Make sure that 'setenv' form INET is also sourced before launching the IDE. That script adds the inet spcific packages to the PYTHONPATH. |
Thanks, sourcing setenv seems to fix the problem when launching omnetpp from the command line. |
The problem is that the 'setenv' script of inet is obviously INET specific. When you start the OMNeT++ IDE, there is absolutely no knowledge what kind of models will be used and the verious paths (NED, PYTHON etc. MUST be set before the IDE so the IDE process could inherit it). Apart from sourcing the OMNeT++ and INET setenv scripts from your |
Hello,
for some reason I cannot use the Debug mode in INET anymore and I cannot figure out why.
For testing I completely reinstalled OMNeT++ 6.0.3 in a new folder to ensure there is not some old configuration issue.
I can use the debug mode for these OMNeT++ samples (e.g. the TicToc sample)
Additionally I created a new workspace in which I installed INET 4.5.2 from the INET v4.5.2 git tag and another new workspace where I've let OMNeT++ install INET automatically.
When I try to run any configuation in debug mode (e.g. timeawareshaper), it builds the project and I'm prompted with the following error:
For every subsequent run where I try to run the configuration in debug mode I get the following error:
When I delete the .metadata folder in my workspace and open the workspace again I jump back to the first error.
I start OMNeT++ in a conda environment:
Conda Environment extract
Does someone have an idea how to fix this?
The text was updated successfully, but these errors were encountered: