Yeah I got this far, but the stack trace doesn't have the symbols. The guy I'm working with said it might be because the addons use dynamically linked libraries instead of statically linked libraries...
By the way, I think a jenandre used to work at my company.
What library is missing the symbols? You may be able to tell by the stack trace. You should get symbols for something at least before it's lost. Examine that frame to see what it's doing. Linking some non-debug library w/ a debug executable just means that gdb won't display the symbols when it enters code for that library. But if your addons are built with -g you'll get the symbols for the addon before it starts calling the other library it is using.
Btw, people often write javascript wrappers that manually refer to the build/Release/.node version instead of the debug version (which will get added to build/Debug/.node). Check that first.
Even if you are using dynamically linked libraries (like the zmq addon does), you can always build debug versions of those to get all of the symbols (try CFLAGS=-g when ./configure).
We never make it to symbol-land in the bt, so I'm assuming it's because we never get into a debug library at all. I will make sure the js is referring to the correct version of the addon though.
My next step is probably going to be to try and figure out how to get every library to build with symbols. Thanks for the help. :D
Comments
Crashes (that can be reliably reproduced) should be way easier to debug than memory leaks.
a) build a `debug` version of node (building node from source creates a node_g version which is a debug version)
b) build a `debug` version of all of the c++ addons in your node_modules folder (node-gyp build -d for each addon)
c) start gdb with the debug version of node: `gdb ./node_g`
d) in gdb, run your node script using `run <script.js>` -- add any other options
e) wait for it to crash, and then type `bt` - you'll see the location of the crash which should give you a good starting place.
Yeah I got this far, but the stack trace doesn't have the symbols. The guy I'm working with said it might be because the addons use dynamically linked libraries instead of statically linked libraries...
By the way, I think a jenandre used to work at my company.
What library is missing the symbols? You may be able to tell by the stack trace. You should get symbols for something at least before it's lost. Examine that frame to see what it's doing. Linking some non-debug library w/ a debug executable just means that gdb won't display the symbols when it enters code for that library. But if your addons are built with -g you'll get the symbols for the addon before it starts calling the other library it is using.
Btw, people often write javascript wrappers that manually refer to the build/Release/.node version instead of the debug version (which will get added to build/Debug/.node). Check that first.
Even if you are using dynamically linked libraries (like the zmq addon does), you can always build debug versions of those to get all of the symbols (try CFLAGS=-g when ./configure).
We never make it to symbol-land in the bt, so I'm assuming it's because we never get into a debug library at all. I will make sure the js is referring to the correct version of the addon though.
My next step is probably going to be to try and figure out how to get every library to build with symbols. Thanks for the help. :D