-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/12/12 14:43, Paul Menzel wrote:
> The following code caused the segmentation fault.
By far the most likely cause is some other library or the app itself
stomping on SQLite's memory. SQLite is on every Android device, every iOS
device,
On 4 December 2012, Paul Menzel wrote:
After doing `apt-get source sqlite3` and building it myself with
`debuild -b -us -uc`, I have the source file `sqlite3.c` and I am able
to look at the code statements.
> The backtrace from the core dump file is the following.
>
> Thread 1 (Thread
Am Sonntag, den 02.12.2012, 22:49 +0100 schrieb Paul Menzel:
> using Debian Sid/unstable with self-built Evolution 3.4.4 and
> libsqlite3-0 3.7.14.1-1, Evolution crashed with a segmentation fault.
>
> pool[15522]: segfault at 5 ip b69bafe3 sp 8acf0850 error 6 in
>
On Tue, Dec 4, 2012 at 9:35 AM, Paul Menzel <
paulepan...@users.sourceforge.net> wrote:
>
> Could this please be added to the bug tracker? Unfortunately this
> backtrace is all I have got.
>
Just because SQLite appears in a stack trace does not mean that SQLite is
at fault here. In fact, far
Dear SQLite folks,
Am Sonntag, den 02.12.2012, 22:49 +0100 schrieb Paul Menzel:
> using Debian Sid/unstable with self-built Evolution 3.4.4 and
> libsqlite3-0 3.7.14.1-1, Evolution crashed with a segmentation fault.
>
> pool[15522]: segfault at 5 ip b69bafe3 sp 8acf0850 error 6 in
>
Dear SQLite folks,
using Debian Sid/unstable with self-built Evolution 3.4.4 and
libsqlite3-0 3.7.14.1-1, Evolution crashed with a segmentation fault.
pool[15522]: segfault at 5 ip b69bafe3 sp 8acf0850 error 6 in
libsqlite3.so.0.8.6[b69a4000+ac000]
The backtrace from the core dump
6 matches
Mail list logo
