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. if it's not ...
i might still have the core file around if you need to inspect
some state...
that might be definitely useful, as i might find the triggering input
that way. note that it will contain the plain text of some messages (the
current one in full, and the remainder(s) of the biggest one(s), but
what exactly would be possible to reconstruct depends on the allocator's
behavior).
oh, and your config file might be useful, just in case this is triggered
by a less tested feature.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
