couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2045) Trace trap error while starting CouchDB
Date Tue, 04 Feb 2014 04:34:08 GMT


Paul Joseph Davis commented on COUCHDB-2045:

IIRC we need to avoid linking against CoreFoundation in driver/NIF code. There was something
about one of the OS X main libraries needing to be initialized from the main thread of a program
and would crash randomly if that didn't happen. What really needs to happen is that we figure
out why your machine is trying to link against CoreFoundation in the first place.

Are you perhaps on OS X 10.9? I haven't upgraded yet but I could see there being something
funky in the ICU libs on the newer OS.

> Trace trap error while starting CouchDB 
> ----------------------------------------
>                 Key: COUCHDB-2045
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: BigCouch
>            Reporter: Russell Branca
> I ran into an error today in the 1843-feature-bigcouch branch, where running `./rel/dev1/bin/couchdb`
would result in the VM crashing with a trace trap error. I tracked this down to the couch_primary_sup
child spec for the `collation_driver` when calling `couch_drv:start_link()`, and more particularly,
I was able to reproduce this error in a standard Erlang shell by running the command: `erl_ddll:load("/tmp/bigcouch/rel/dev1/lib/couch-2f254d9/priv",
> After poking around with things, I ended up stumbling upon:
(linked from I was able
to resolve the error by doing `export DYLD_INSERT_LIBRARIES=/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation`
in the shell prior to executing `./rel/dev1/bin/couchdb`.
> This seems like a logical addition to the flags set in `src/couch/rebar.config.script`,
but I'm not familiar with CoreFoundation, so I don't have a recommendation on the proper way
to do this across platforms.

This message was sent by Atlassian JIRA

View raw message