|
[Rivet] debugging RivetJames William Monk xls701 at ku.dkTue Oct 27 19:17:13 GMT 2015
Hi, Does anyone have a good technique for debugging Rivet? One downside of it running inside a Python shell is that when I have a seg fault the only info I get is the line of the python script on which the crash happens, which isn’t very enlightening. Of course I am on a mac and therefore using lldb instead of gdb, but there is a Python API for all the lldb functionality, so you’d think it would play nicely, but doesn’t seem to - all the examples for lldb I have seen assume you have a compiled executable that you want to debug interactively from a Python shell, not debug the calls to Python bindings themselves. I currently have what looks like a vector out of bounds error, but trying to find where it is happening is infuriating! cheers, James
More information about the Rivet mailing list |