On 5/29/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> p &sqlite3InitCallback
>
(gdb) p $sqlite3InitCallback
$1 = void
g.
> Try "info shared" in gdb. Not sure whether that works on OSX,
> though.
>
Worked beautifully!
The smoking gun: something is hauling in the system provided sqlite3
On 5/29/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> The question for python-dev is "how can I debug that further, and where
> should I submit a patch" :-)
>
I have no problem with that. :-)
> > (gdb) info threads
> > * 1 process 18968 local thread 0x1003 0x900e41d1 in strtol_l ()
> > (gdb
On 5/29/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
> What happens when you use the binary installer at python.org? This is
> build with a newer version of sqlite as well (because the installer
> supports OSX 10.3).
>
Hmmm. I hadn't thought of checking the sqlite version in there. I did
use the
First of all 1000 apologies if this is the wrong list. Please redirect
me if necessary.
I'm attempting to build python 2.5.1 fat binaries on OSX and
statically link to a newer sqlite than what ships with OSX. (3.3.17).
I'm getting "Bus Error" early when I run my app. If I turn on a lot of
malloc
