On Sat, Oct 25, 2014 at 6:15 AM, Paul Menzel <
paulepan...@users.sourceforge.net> wrote:
>
> thank you a lot for the analysis leading to a solution.
>
> Was it just bad luck that such a change to use different code paths is
> done for a bug fix release (3.8.6 to 3.8.7)? Or don’t you use semantic
Dear Richard,
Am Mittwoch, den 22.10.2014, 21:53 -0400 schrieb Richard Hipp:
> On Wed, Oct 22, 2014 at 5:14 PM, Paul Menzel wrote:
> > after the upgrade of libsqlite3 from 3.8.6 to 3.8.7 Evolution crashes
> > with a segmentation fault.
> >
> > pool[6371]: segfault at 0 ip (null) sp
regression] SQLite 3.8.7 causes Evolution to crash
>
On Wed, Oct 22, 2014 at 5:14 PM, Paul Menzel <
paulepan...@users.sourceforge.net> wrote:
Dear SQLite folks,
after the upgrade of libsqlite3 from 3.8.6 to 3.8.7 Evolution crashes
with a segmentation fault.
pool[6371]: s
On Wed, Oct 22, 2014 at 5:14 PM, Paul Menzel <
paulepan...@users.sourceforge.net> wrote:
> Dear SQLite folks,
>
>
> after the upgrade of libsqlite3 from 3.8.6 to 3.8.7 Evolution crashes
> with a segmentation fault.
>
> pool[6371]: segfault at 0 ip (null) sp a67d26ec error 14
>
> Several
Dear SQLite folks,
after the upgrade of libsqlite3 from 3.8.6 to 3.8.7 Evolution crashes
with a segmentation fault.
pool[6371]: segfault at 0 ip (null) sp a67d26ec error 14
Several people have reproduced this [1].
Milan, one of the main developers of Evolution, analyzed the crash a
Dear SQLite folks,
after the upgrade of libsqlite3 from 3.8.6 to 3.8.7 Evolution crashes
with a segmentation fault.
pool[6371]: segfault at 0 ip (null) sp a67d26ec error 14
Several people have reproduced this [1].
Milan, one of the main developers of Evolution, analyzed the crash a
6 matches
Mail list logo
