On Wed, 2017-11-15 at 19:36 +0100, deloptes wrote:
> Patrick Ohly wrote:
> > On Wed, 2017-11-15 at 13:48 +0100, deloptes wrote:
> > > I don't have the time now to deal with it, so it is just FYI. I
> > > hope
> > > we can follow up on that next.
> > >
> > > regards
> > >
> > >
> > >
Patrick Ohly wrote:
> On Wed, 2017-11-15 at 13:48 +0100, deloptes wrote:
>> Hi Patrick,
>>
>> I finally got a response from openobex and the secret was in the
>> UPGRADING document.
>
> Is that response somewhere public?
>
Well their site is down, sourforge is outdated, I found only the
Hi,
Patrick Ohly wrote:
> I haven't seen that email, but perhaps I just missed it. Please send
> again and let me know here what the subject is.
I sent now from my yahoo mail. I couldn't see anything interesting there,
but I am also not an expert.
I couldn't do much this week, I just found out
On Tue, 2017-11-07 at 00:30 +0100, deloptes wrote:
> On Thu, 2017-11-02 at 22:27 +0100, deloptes wrote:
> > > Patrick Ohly wrote:
> > >
> > > > On Sat, 2017-10-07 at 19:31 +0200, deloptes wrote:
> > > > > Patrick Ohly wrote:
> > > > >
> > > > > > Perhaps send it to me privately? I'm not sure
Hi thanks
Patrick Ohly wrote:
> On Thu, 2017-11-02 at 22:27 +0100, deloptes wrote:
>> Patrick Ohly wrote:
>>
>> > On Sat, 2017-10-07 at 19:31 +0200, deloptes wrote:
>> > > Patrick Ohly wrote:
>> > >
>> > > > Perhaps send it to me privately? I'm not sure whether I'll find
>> > > > anything
On Thu, 2017-11-02 at 22:27 +0100, deloptes wrote:
> Patrick Ohly wrote:
>
> > On Sat, 2017-10-07 at 19:31 +0200, deloptes wrote:
> > > Patrick Ohly wrote:
> > >
> > > > Perhaps send it to me privately? I'm not sure whether I'll find
> > > > anything either, though.
> > >
> > > Can't we add
Patrick Ohly wrote:
> On Sat, 2017-10-07 at 19:31 +0200, deloptes wrote:
>> Patrick Ohly wrote:
>>
>> > Perhaps send it to me privately? I'm not sure whether I'll find
>> > anything either, though.
>>
>> Can't we add some debug code in syncevo or obex to get the type of
>> event is causing the
On Sat, 2017-10-07 at 19:31 +0200, deloptes wrote:
> Patrick Ohly wrote:
>
> > Perhaps send it to me privately? I'm not sure whether I'll find
> > anything either, though.
>
> Can't we add some debug code in syncevo or obex to get the type of
> event is causing the trouble?
> The message I get
Patrick Ohly wrote:
> Perhaps send it to me privately? I'm not sure whether I'll find
> anything either, though.
Can't we add some debug code in syncevo or obex to get the type of event is
causing the trouble?
The message I get after including libsynthesis in syncevo is a bit different
(more
On Fri, 2017-10-06 at 23:01 +0200, deloptes wrote:
> Patrick Ohly wrote:
> Please note that the reference used with obex1.5 is not build this
> way. Let
> me know if I have to do the same with obex1.5
That would only be necessary if we wanted to debug obex1.5 at the
source level. This doesn't
Patrick Ohly wrote:
> Typically, during my development work I build with
> --disable-shared --enable-static and --with-synthesis-
> src=.../libsynthesis where "libsynthesis" is the source dir of
> libsynthesis.
>
> That way, I get a single executable that has the right compile flags
> and all
On Tue, 2017-10-03 at 10:35 +0200, deloptes wrote:
> Patrick Ohly wrote:
>
> > Interesting :-/ Perhaps try running under valgrind to root-cause
> > this
> > issue?
> >
>
> I was thinking the memory errors in valgrind were related to the
> tdepim
> code, but it looks like it fails in the sync
On Sat, 2017-09-30 at 21:17 +0200, Patrick Ohly wrote:
> So that's still the same error. The question now is, where does this
> "Unknown response" come from? What is the actual response code and
> where was it set?
Another way to approach this might be to take network traffic dumps
with wireshark
Patrick Ohly wrote:
> On Fri, 2017-09-29 at 22:22 +0200, deloptes wrote:
>> I'm not sure I did all correctly
>>
>> export LD_LIBRARY_PATH=/data-backup/DEVELOPMENT/Projects/tde-
>> sup/sync_debug/openobex-1.7.2-Source/debian/build/lib
>
> Looks like you are building libopenobex via the Debian
On Fri, 2017-09-29 at 22:22 +0200, deloptes wrote:
> I'm not sure I did all correctly
>
> export LD_LIBRARY_PATH=/data-backup/DEVELOPMENT/Projects/tde-
> sup/sync_debug/openobex-1.7.2-Source/debian/build/lib
Looks like you are building libopenobex via the Debian packaging.
That's just
I'm not sure I did all correctly
export
LD_LIBRARY_PATH=/data-backup/DEVELOPMENT/Projects/tde-sup/sync_debug/openobex-1.7.2-Source/debian/build/lib
SYNCEVOLUTION_DEBUG=10 ./src/syncevolution --daemon=no -r loglevel=6
nokia_N9
addressbook
DEBUG 00:00:02] ready to sync
[DEBUG 00:00:02] starting
16 matches
Mail list logo
