On 2015/04/01 17:39, Zé Loff wrote: > On Wed, Apr 01, 2015 at 01:20:49PM -0300, Gleydson Soares wrote: > > could you try to reproduce again? > > isync doesn't segs here. (@amd64) > > mbsync (not this version though, the one on amd64 -current) segfaults > every time it can't resolve the server name, and has been doing so for a > while now. I've been meaning to report it for a while now, but never > bothered / got the time to address it properly. Maybe that's what > Dmitrij is seeing. > > > > > On Wed, Apr 1, 2015 at 12:59 PM, Edd Barrett <[email protected]> wrote: > > > On Mon, Mar 30, 2015 at 12:55:33PM +0200, Dmitrij D. Czarkoff wrote: > > >> Any test reports? > > > > > > I've been using this for a while (mbsync at least). > > > > > > I notice that the isync command segs. Not looked into it, but I have no > > > .isyncrc file (only a .mbsyncrc), so that may be why. > > > > > > -- > > > Best Regards > > > Edd Barrett > > > > > > http://www.theunixzoo.co.uk > > > > > > > > > > > -- > > O< ascii ribbon campaign - stop html mail - www.asciiribbon.org > > > > -- >
C'mon, you guys know that "it crashes" is a useless report. Backtrace?!
