couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Branca (JIRA)" <j...@apache.org>
Subject [jira] [Created] (COUCHDB-2045) Trace trap error while starting CouchDB
Date Tue, 04 Feb 2014 00:48:09 GMT
Russell Branca created COUCHDB-2045:
---------------------------------------

             Summary: Trace trap error while starting CouchDB 
                 Key: COUCHDB-2045
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2045
             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",
"couch_icu_driver").`

After poking around with things, I ended up stumbling upon: http://openradar.appspot.com/7209349
(linked from http://erlang.org/pipermail/erlang-questions/2010-April/050563.html). 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
(v6.1.5#6160)

Mime
View raw message