On Tue, 2010-06-22 at 15:07 +0100, Peter Robinson wrote:
> > This is the source code:
> >
> > DBusConnection *g_dbus_setup_bus(DBusBusType type, const char *name,
> > gboolean unshared,
> > DBusError *error)
> > {
> > DBusConnection *connection;
> >
> > DBG("type %d name %s error %p", type, name, error);
> >
> > connection = unshared ? dbus_bus_get_private(type, error) :
> > dbus_bus_get(type, error);
> >
> > There's really no chance in the C source code to mangle "error". Must
> > happen inside the compiler generated code or in the dbus functions.
> > Again, valgrind might show something.
>
> Sorry about the delay on this, its been somewhat busy of late!
>
> The remaining error in 1.0 seems to be the dbus_error_is_set crash
> which stops it from running at all on Fedora 13. I pushed out 1.0 to
> updates-testing yesterday and already have half a dozen dupes. The bug
> with all the dupes is below, let me know if you need more information
> and I'll try and sort it out.
Are you able to reproduce the problem? Can you
run /usr/libexec/syncevo-dbus-server under valgrind, then cause it to
crash by also starting the command line?
My hope is that the valgrind output shows a bit more than the stack back
traces that are currently in the bug reports.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
