Am Freitag, 31. Juli 2020, 10:04:57 CEST schrieb David Llewellyn-Jones:
> One final point: I think these mailing lists are supposed to be on ice
> now, so people may not be following them so much. You might get a better
> response at forum.sailfishos.org.
Just to a some tip to this topic discourse
szo...@gmail.com wrote:
> Yeah I'm pretty sure it's the moving stage, hardly anyone reads any
> development topics and it will take a while for people to move from this
> list probably some won't ever as they will not notice :( as even my very
> basic question didn't get any reply in 2 days, maybe
Yeah I'm pretty sure it's the moving stage, hardly anyone reads any development
topics and it will take a while for people to move from this list probably some
won't ever as they will not notice :( as even my very basic question didn't get
any reply in 2 days, maybe jolla can rethink canning thi
David Llewellyn-Jones wrote:
> I'm not fully clear on whether you're after debugging (e.g. using gdb)
> or logging output.
>
I need log output. Debugger might be a next stage, though in that case
wireshark and log output could help most. The problem is I want to find out
why it is stuck, but it
On 31/07/2020 09:11, deloptes wrote:
[snip]
> I see in buteo-syncml that the mentioned OBEX_HandleInput() is called in a
> loop while waiting for input.
> My problem is and hence my request here, that there is no debugging log from
> the obex transport, because it gets started in a thread by msyncd
Hello,
Yesterday (July 30th) at 08:00 UTC the Sailfish SDK 3.2 was released to Early
Access users. Please, check out the release notes from
https://forum.sailfishos.org/t/release-notes-sailfish-sdk-3-2-early-access/1241[1]
.
Attention: This is the last announcement posted in this mailing list.
