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

Segfault on conda-build with JPEG parameter struct mismatch: library thinks size is 632, caller expects 664 #2699

Closed
osrf-migration opened this issue Mar 6, 2020 · 3 comments
Labels
all bug Something isn't working gui major

Comments

@osrf-migration
Copy link

Original report (archived issue) by Wolf Vollprecht (Bitbucket: Wolf).


Hi all,

I have an almost working build of gazebo11 on conda-forge! I can start the gazebo server, and also check that some of the default messages are sent successfully.

However, the gazebo client crashes after printing the following in verbose mode:

(gazz) ~/Programs:$ gzclient --verbose
Gazebo multi-robot simulator, version 11.0.0
Copyright (C) 2012 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org

[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://127.0.0.1:11345
[Msg] Publicized address: 10.12.199.184
[Wrn] [Event.cc:61] Warning: Deleting a connection right after creation. Make sure to save the ConnectionPtr from a Connect call
[Wrn] [GuiIface.cc:119] JPEG parameter struct mismatch: library thinks size is 632, caller expects 664
Segmentation fault (core dumped)

When launching with gdb attached, the backtrace only shows:

Thread 1 "gzclient" received signal SIGSEGV, Segmentation fault.
0x00007ffff3d034de in ____longjmp_chk () from /lib64/libc.so.6
(gdb) bt
#0 0x00007ffff3d034de in ____longjmp_chk () from /lib64/libc.so.6
#1 0x40554107a766ecb0 in ?? ()
Backtrace stopped: Cannot access memory at address 0x4dfaea878771419f

I can see the splashscreen rectangle (without any content), but unfortunately that’s it.

I am just wondering if someone here knows anything?

@osrf-migration
Copy link
Author

Original comment by Silvio Traversaro (Bitbucket: traversaro).


I think that based on the discussion on conda-forge/gazebo-feedstock#11, we can close this issue?

TL;DR: It turns out that the problem was that Qt and Freeimage were linking two different (ABI-incompatible) versions of libjpeg.

@osrf-migration
Copy link
Author

Original comment by Wolf Vollprecht (Bitbucket: Wolf).


yes, thanks again silvio for helping with this!

works fine now locally, and I will take care of rebuilding freeimage on conda-forge!

@osrf-migration
Copy link
Author

Original comment by Wolf Vollprecht (Bitbucket: Wolf).


  • changed state from "new" to "resolved"

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

No branches or pull requests

1 participant