If I have sent these questions to the wrong forum, can someone please tell me where I shall send them.
vmware-vmrc in file vmware-vmrc-linux-x86-3.0.0-309851.xpi at
https://github.com/vmware/rvc/downloads is not compatible with new versions of
glibmm-2.4 (from version 2.28, released 2011-04-15).
Is there a newer version of vmware-vmrc that can be used together with the
newest versions of glibmm?
For those who don't know: Glibmm is open source software, used by several of
VMware's programs, among them vmrc.
The long story (primarily intended for a VMware software developer)
Glibmm bug 681206 (https://bugzilla.gnome.org/show_bug.cgi?id=681206) complains
about segfaults in Glib::OptionGroup::CppOptionEntry::release_c_arg() when running vmware-vmrc.
The incompatibility between glibmm and vmware-vmrc arose when I fixed bug
https://bugzilla.gnome.org/show_bug.cgi?id=589197. I changed the use of
protected data member Glib::OptionGroup::map_entries_, without thinking of the
possibility that an application program can derive a class from
Glib::OptionGroup and use protected data for its own purposes. Now I've seen
that vmware's class lui::OptionGroup in libvmwareui.so.0 does just that.
Have you noticed this problem, and modified lui::OptionGroup?
If not, are you willing to modify it?
If not, are you willing to let me see the source code of lui::OptionGroup?
Then I can probably suggest a suitable modification.
In the worst case, I suppose I will have to modify Glib::OptionGroup, to once
again make it compatible with some existing version of vmware-vmrc. That task
would be easier if I can have a look at the source code of lui::OptionGroup,
to see exactly what it does. I can't just undo the modifications of bug 589197.
That bug fix introduced new functionality in Glib::OptionGroup that other
people are probably using now.
It's possible that I broke API when I fixed bug 589197. I'm not sure if the
exact use of protected data members is considered part of the API.
I have previously posted these questions to the VMware Player forum, without
getting an answer. Although VMware has published lots of info on the web,
I have not found a good way to ask technical questions to VMware's developers
without being a VMware customer.