Hey there again, Usually when I get segfaults, it's because my own C++ code does something stupid. When I run it through the debugger, it always lets me know where the problem is in the C++ code (that's how I know it's the C++ code causing the problem). Imagine my surprise as I got something to segfault in Python.
For some reason the top block code is causing a segfault for me, and I don't know why. Is there anything in top block that could cause this? Or, is it more likely likely a problem with my own python code? Here's the debug output: -> tb.run() (Pdb) step --Call-- > /usr/local/lib/python2.5/site-packages/gnuradio/gr/top_block.py(50)run() -> def run(self): (Pdb) step > /usr/local/lib/python2.5/site-packages/gnuradio/gr/top_block.py(51)run() -> top_block_run_unlocked(self._tb) (Pdb) step --Call-- > /usr/local/lib/python2.5/site-packages/gnuradio/gr/gnuradio_swig_py_runtime.py(1577)top_block_run_unlocked() -> def top_block_run_unlocked(*args): (Pdb) step > /usr/local/lib/python2.5/site-packages/gnuradio/gr/gnuradio_swig_py_runtime.py(1579)top_block_run_unlocked() -> return _gnuradio_swig_py_runtime.top_block_run_unlocked(*args) (Pdb) step Segmentation fault (core dumped) Any help you could give me would be greatly appreciated. -Ben _________________________________________________________________ Put your friends on the big screen with Windows Vista® + Windows Live™. http://www.microsoft.com/windows/shop/specialoffers.mspx?ocid=TXT_TAGLM_CPC_MediaCtr_bigscreen_012008 _______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
