This was fixed in 0.3-2
** Changed in: ndesk-dbus-glib (Ubuntu)
Status: Fix Committed => Fix Released
--
segfault in g_io_add_watch on PPC
https://bugs.launchpad.net/bugs/127424
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
** Bug watch removed: 'Bug tracker at http://bugs.ximian.com/' #77968
http://bugs.ximian.com/show_bug.cgi?id=77968
** Bug watch added: Ximian Bug Tracker #77968
http://bugzilla.ximian.com/show_bug.cgi?id=77968
--
segfault in g_io_add_watch on PPC
https://bugs.launchpad.net/bugs/127424
You
What i'm saying is that imo it's not by accident. I think they used that
attribute to be able to pass the IOChannel struct where a GIOChannel
pointer is needed. IOChannel is a value-type and its layout is
sequential, hence there should be no padding or reordering in the
fields. So passing an IOChan
That's all correct, LayoutKind.Sequential will care that the struct is
passed to native functions with that layout, i.e. not reordered. At
least that's my understanding of that attribute.
But the GLib functions don't want this managed struct or the native
equivalent to it, instead they want a "nat
Hi slomo,
thanks for looking at this.
AFAIU the IOChannel struct in GLib.IO.cs has a StructLayout
(LayoutKind.Sequential) attribute so that passing IOChannel by value or passing
IOChannel.Handle *should* have the same result. And indeed this works on x86.
This might be a regression introduced by
Hi,
I already fixed this in Debian, essentially your patch plus a few places with
the same issue. It's really a bug in ndesk-dbus-glib, the GLib functions
require a native GIOChannel struct (which is the IOChannel.Handle variable) and
not a managed IOChannel struct.
The version from Debian shou
for the brave ppc users that want to try the patch:
apt-get source ndesk-dbus-glib
cd ndesk-dbus-glib-0.3
sudo apt-get build-dep ndesk-dbus-glib
wget http://launchpadlibrarian.net/8542716/ndesk_glib_workaround.diff
patch -p0 https://bugs.launchpad.net/bugs/127424
You received this bug notification
This seems a bug in mono on ppc actually, see
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/122496/comments/5
for details.
Attached is a patch to workaround the bug. This makes tomboy and f-spot start
again here.
Note that this is just a workaround, a better way to fix this directly in mon
