On 2021-11-18 16:57:33, Oswald Buddenhagen wrote:
> On Thu, Nov 18, 2021 at 10:34:43AM -0500, Antoine Beaupré wrote:
>>$2 = {
>> data = 0x559f9c642e00 "X-TUID: GovLn9FNVKrB\n[placeholder] \n It is
>> anticipated that there will eventually come a time where the\n third party
>> ecosystem surrou
On Thu, Nov 18, 2021 at 10:34:43AM -0500, Antoine Beaupré wrote:
$2 = {
data = 0x559f9c642e00 "X-TUID: GovLn9FNVKrB\n[placeholder] \n It is anticipated
that there will eventually come a time where the\n third party ecosystem surrounding
Python 3 is sufficiently mature\n for this recommendat
On 2021-11-18 09:59:15, Antoine Beaupré wrote:
> i looked a bit at the backtrace again and it seems the crash happens on
> line 534 in sync.c, which is:
>
> (gdb)
> #5 0x559f9b9b01a7 in copy_msg_convert (vars=0x559f9c6445a0,
> out_cr=, in_cr=) at ./src/sync.c:534
> 534 free( in_buf
On 2021-11-18 10:22:31, Oswald Buddenhagen wrote:
> On Wed, Nov 17, 2021 at 07:57:59PM -0500, Antoine Beaupré wrote:
>>totally frustrating, on the one hand. on the other hand: yay bug
>>solved?
>>:p
>>
> :'-D
>
>>maybe the gdb backtrace could be of use?
>>
> depends on how local the problem is. if
On 2021-11-17 10:17:58, Oswald Buddenhagen wrote:
> On Wed, Nov 17, 2021 at 08:08:22AM +0900, Norbert Preining wrote:
>>Today I got a bug report about a crash including a backtrace:
>>
> i know, i watch the debian package. you don't need to forward anything
> to me. in fact, i was about to reply d
On Wed, Nov 17, 2021 at 07:57:59PM -0500, Antoine Beaupré wrote:
totally frustrating, on the one hand. on the other hand: yay bug
solved?
:p
:'-D
maybe the gdb backtrace could be of use?
depends on how local the problem is. if it's near the crash site,
careful code review might reveal it.
Hi Oswald,
> i know, i watch the debian package. you don't need to forward anything to me.
Thanks a lot! This is absolutely great.
If there is anything you would like to see in the Debian package, please
reach out, I will take care of it.
All the best
Norbert
--
PREINING Norbert
On Wed, Nov 17, 2021 at 08:08:22AM +0900, Norbert Preining wrote:
Today I got a bug report about a crash including a backtrace:
i know, i watch the debian package. you don't need to forward anything
to me. in fact, i was about to reply directly on the bts before it
occurred to me to check the
Dear all,
Debian maintainer of isync here.
I recently took over maintainership (isync was more or less orphaned in
Debian) and update to 1.4.3.
Today I got a bug report about a crash including a backtrace:
> Before the upgrade (1.3.0-2.2, on bullseye), I am able to run mbsync
> without too many
