-
Notifications
You must be signed in to change notification settings - Fork 20
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
gdk-pixbuf2-2.40.0-5.sgug trigger error gdk-pixbuf-query-loaders #167
Comments
Hello - thank you for your report. This is a little strange. When possible can you please provide:
And we see if anything obvious crops up. |
(If anyone else gets the zen to look at this - originally I believe we'd fixed these trigger coredumps in a46f00e - which should be in 0.0.7 - but we'll have to see since it's not clear the real root cause yet). |
-Mike |
Great thanks for your patience -> I see I am an idiot and assumed the wrong thing (rpm crash) - even though you told me it was gdk-pixbuf-query-loaders too ! Acknowledged + apologies. The log confirms at least that RPM is installing as intended - now I am up to speed :-) I guess we'll need to rebuild gdk-pixbuf2 in debug non-strippped and then re-run as you demonstrated and let it core dump, then use gdb to obtain a stack trace. (Goes to rebuild 'gdk-pixbuf2' in debug) Install this with:
Then re-run manually like you did in original report - and let it coredump.
Perhaps other useful info might be the output from:
Thank you! |
GDB with symbols: [sgugshell root@saiph /]# gdb /usr/sgug/bin/gdk-pixbuf-query-loaders core
and thus can't determine the size of that function's stack frame. OUTPUT for par here -Mike |
Thank you for getting the trace - I think we have a good picture of what's going on (although why only certain machines hit it is a little head scratchy!). Reading the stack trace from bottom to top - we see the following:
This is because our gdb has issues working out the root of stack frames for pthreaded applications. We have to work with this for now.
Looks like the binary uses/is linked to
Ah - here's the problem - something has pulled in the IRIX C++ shared library - and now the binary is mixing and matching between libstdc++ and MIPSPro C++ libraries - no surprise this doesn't work out well. How can this happen - well in 0.0.7beta there is native file monitoring as a module in If you just want to see if this makes a difference, you can uninstall There wasn't time to fix this in 0.0.7beta unfortunately, but it has been fixed since then to avoid any linking to the MIPSPro C++ lib. If you are willing + up to it, you can try to |
Ok let's do this.. Step 1) Remove glib2-fam Test [sgugshell root@saiph /]# gdk-pixbuf-query-loaders --update-cache No Core Dump.. Looks good I'll look at building the WIP version of the fam's and see how that goes. -Mike ADDED: gtk3-demo now runs fine and pidgin starts up as expected. |
The triggerin and triggerpostun in the SPEC file fail on an O2 and Indigo2 (as reported on the SGUG forum)
The failure is the update cache.
[sgugshell root@saiph /]# gdk-pixbuf-query-loaders --update-cache
Bus error (core dumped)
-Mike
The text was updated successfully, but these errors were encountered: