-
Notifications
You must be signed in to change notification settings - Fork 44
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
ABI change in libfm.so.4 in recent commit #104
Comments
Actually
|
The following 2 commit: lxde@b0545e0 lxde@2854a4c broke libfm.so ABI because this changed the size of `struct _FmConfig` . Restore libfm.so ABI compared to before. Fixes lxde#104 .
I'm afraid I was too hasty with your pull request and need to revert it and bump the major version of libfm instead. Otherwise, configuring Right now, pcmanfm is still safe because all uses of the new configuration settings are safeguarded with FM_CHECK_VERSION. But |
Or create |
Or create INIT_FMCONFIG_WITH_SIZE with specifying size to read? |
What you mean by that? |
The ABI remains stable with anonymous unions:
Unless I missed something, this is how I'm going to fix #105. |
Currently
|
But maybe the above method is overdone. |
This seems reasonable to me. |
Applied. |
Looks like due to
b0545e0
2854a4c
the size of
struct _FmConfig
got changed and this resulted in ABI change in libfm.so.4.Downside bug report
https://bugzilla.redhat.com/show_bug.cgi?id=2333955
is perhaps due to the following condition
libfm between these commits includes 2854a4c
Then pcmanfm causes segfault.
The downside bug's backtrace seems to be sugesting that
_cfg_mon
in_FmConfig
is not initialized to 0 despite thatg_object_new
is called.The text was updated successfully, but these errors were encountered: