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

Wrong ogre library loaded at runtime when Ogre1.x and Ogre2.x are both installed #36

Open
osrf-migration opened this issue Nov 16, 2018 · 6 comments
Labels
bug Something isn't working

Comments

@osrf-migration
Copy link

Original report (archived issue) by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).


Description

Compilation works fine and the correct version of ogre libraries are linked but the wrong version of ogre library gets loaded during run time. It always loads the first libOgreMain.so it finds in the path, resulting in memory corruption when a test or a demo is run.

Steps to Reproduce

  1. Install ogre 1.9 (e.g. libogre-1.9-dev)

  2. install ogre 2.1 (e.g. from source into $HOME/local)

  3. build ign-rendering

  4. run make test

Expected behavior:

tests run without crashing

Actual behavior:

test crashes with a msg about memory corruption

@osrf-migration
Copy link
Author

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).


  • Edited issue description

2 similar comments
@osrf-migration
Copy link
Author

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).


  • Edited issue description

@osrf-migration
Copy link
Author

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).


  • Edited issue description

@osrf-migration
Copy link
Author

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).


  • Edited issue description

@osrf-migration
Copy link
Author

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).


I believe it's because of this issue that ogre2 is not listed as one of the RENDER_ENGINE_VALUES here, is that right?

I think this means no tests are being run for ogre2 at all? If that's the case, I'd suggest:

  1. Changing ogre to ogre2 on that list, so we test the main engine we're focusing on.
  2. Splitting the tests into separate executables, so that we can test both ogre 1 and 2.

@osrf-migration osrf-migration added major bug Something isn't working labels Apr 15, 2020
@chapulina chapulina removed the major label May 25, 2020
@chapulina
Copy link
Contributor

The tests are being moved to ogre2 on #83

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants