Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

28172838: Segfault when linking against libsqlite3 #15774

Open
openradar-mirror opened this issue Sep 6, 2016 · 0 comments
Open

28172838: Segfault when linking against libsqlite3 #15774

openradar-mirror opened this issue Sep 6, 2016 · 0 comments

Comments

@openradar-mirror
Copy link

Description

Summary:
When using the python sqlite driver and linking against the dylib provided with OSX (/usr/lib/libqlite3.dylib) we can reproducibly cause a segfault. The attached file has the back trace when the segfault occurs. When using the dylib from the homebrew installed version of sqlite it works as expected.

Steps to Reproduce:
Unfortunately, the test suite is proprietary and can't be shared.

Expected Results:
No seg fault.

Actual Results:
Segfault.

Version:
sqlite3, OSX El Capitan 10.11.6 (although it has happened on other OSX versions)

Notes:

Configuration:
Out of the box sqlite3

Attached File:
(lldb) bt

Product Version:
Created: 2016-09-06T19:14:07.117580
Originated: 2016-09-06T00:00:00
Open Radar Link: http://www.openradar.me/28172838

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant