-
Notifications
You must be signed in to change notification settings - Fork 43
Segmentation fault: 11 #28
Copy link
Copy link
Open
Description
Trying out chimera today, and I'm getting the Seg Fault: 11 error others have reported. I used npm install chimera just a few minutes ago. I tried doing gdb node to run my script, and this is the result:
(gdb) run app.coffee
Starting program: /usr/local/bin/node app.coffee
Reading symbols for shared libraries ++++................................................................................................................................. done
Using the chimera in lib
Reading symbols for shared libraries warning: Could not find object file "/Users/catch23/current/node-chimera/build/Release/obj.target/chimera/src/top.o" - no debug information available for "top.cc".
warning: Could not find object file "/Users/catch23/current/node-chimera/build/Release/obj.target/chimera/src/cookiejar.o" - no debug information available for "cookiejar.cc".
warning: Could not find object file "/Users/catch23/current/node-chimera/build/Release/obj.target/chimera/src/chimera.o" - no debug information available for "chimera.cc".
warning: Could not find object file "/Users/catch23/current/node-chimera/build/Release/obj.target/chimera/src/browser.o" - no debug information available for "browser.cc".
......... done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000007
0x0000000102d0cee8 in QString::fromLocal8Bit ()
Looks like there are some hardcoded paths for libraries preventing chimera from running (my user is not catch23)?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels