On Sun, 2013-09-29 at 21:34 +0200, Tino Keitel wrote:
On Sat, Sep 28, 2013 at 20:00:07 +0200, Patrick Ohly wrote:
[...]
> Let's backtrace a bit. What steps are necessary to make it crash without
> valgrind?
I just click on "Sync now" in sync-ui. It segfaults, and if I restart
it as long as the sync is running, it segfaults again without any
further GUI action by the user.
Could it be that no service is selected while running that sync? I was
able to reproduce such a crash in find_updated_source_progress(). Patch
attached.
But that doesn't match your initial stack backtrace at all. Are you
compiling with GTK-2 or GTK-3? If the crash persists, can you recompile
without optimization and capture another stack backtrace?
I use the current Debian sid and the packages from
http://tikei.de/syncevolution-1.3.2/
The crash is independent of the specific version. This has been broken
for a long time.
> And those same steps do not cause it to crash when running
under
> valgrind?
Yes.
Really strange. Perhaps it changes timing so that the method never gets
invoked because the sync completes too quickly.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.