Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segfault in python using HackRF #20

Open
Treyfane opened this issue Jul 26, 2017 · 1 comment
Open

Segfault in python using HackRF #20

Treyfane opened this issue Jul 26, 2017 · 1 comment

Comments

@Treyfane
Copy link

Treyfane commented Jul 26, 2017

Hi there,

I just installed gr-mixalot (after all dependencies) on a Debian 17.04. Cmake/make/make install worked flawlessly and after adding the serial of my HackRF (instead of hackrf=0) it was found.

However, upon calling the line
self.mixalot_pocencode_0 = mixalot.pocencode(1, 1200, 49899, 'Test', 38400)
the py-script crashes:

./pocsagtx_hackrf.py 
linux; GNU C++ version 6.3.0 20170406; Boost_106200; UHD_003.010.002.000-0-ge75c7d6f

gr-osmosdr v0.1.4-98-gc653754d (0.1.5git) gnuradio 3.7.11.1
built-in sink types: uhd hackrf bladerf redpitaya file 
Using HackRF One with firmware 2017.02.1 
mixalot

*** Error in `python2': corrupted double-linked list: 0x0000558a2b2869c0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x7908b)[0x7f6b4d25c08b]
/lib/x86_64-linux-gnu/libc.so.6(+0x84982)[0x7f6b4d267982]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f6b4d268d84]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_Znwm+0x18)[0x7f6b49d98af8]
/usr/lib/x86_64-linux-gnu/libitpp.so.8(_ZN4itpp5ArrayINS_2GFEE8set_sizeEib+0x164)[0x7f6b400b2974]
/usr/lib/x86_64-linux-gnu/libitpp.so.8(_ZN4itpp6modgfxERKNS_3GFXES2_+0x408)[0x7f6b400dcc88]
/usr/lib/x86_64-linux-gnu/libitpp.so.8(_ZN4itpp3BCH6encodeERKNS_3VecINS_3binEEERS3_+0x49f)[0x7f6b400ae2df]
/usr/lib/x86_64-linux-gnu/libitpp.so.8(_ZN4itpp3BCH6encodeERKNS_3VecINS_3binEEE+0x29)[0x7f6b400abae9]
/usr/local/lib/libgnuradio-mixalot.so(+0x5fd5)[0x7f6b404ebfd5]
/usr/local/lib/libgnuradio-mixalot.so(+0x6ade)[0x7f6b404ecade]
/usr/local/lib/libgnuradio-mixalot.so(+0x7b03)[0x7f6b404edb03]
/usr/local/lib/libgnuradio-mixalot.so(+0x86f7)[0x7f6b404ee6f7]
/usr/local/lib/libgnuradio-mixalot.so(_ZN2gr7mixalot9pocencode4makeENS1_9msgtype_tEjjNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEm+0xb3)[0x7f6b404eea03]
/usr/local/lib/python2.7/dist-packages/mixalot/_mixalot_swig.so(+0x131c0)[0x7f6b4070d1c0]
python2(PyEval_EvalFrameEx+0x750e)[0x558a292a61de]
python2(PyEval_EvalCodeEx+0x255)[0x558a2929d4e5]
python2(PyEval_EvalFrameEx+0x6967)[0x558a292a5637]
python2(PyEval_EvalCodeEx+0x255)[0x558a2929d4e5]
python2(+0x115e0e)[0x558a292b9e0e]
python2(PyObject_Call+0x43)[0x558a2928b493]
python2(+0x12c2ee)[0x558a292d02ee]
python2(PyObject_Call+0x43)[0x558a2928b493]
python2(+0x12c027)[0x558a292d0027]
python2(+0xed0b4)[0x558a292910b4]
python2(PyObject_Call+0x43)[0x558a2928b493]
python2(PyEval_EvalFrameEx+0x60df)[0x558a292a4daf]
python2(PyEval_EvalCodeEx+0x255)[0x558a2929d4e5]
python2(PyEval_EvalFrameEx+0x61c9)[0x558a292a4e99]
python2(PyEval_EvalCodeEx+0x255)[0x558a2929d4e5]
python2(PyEval_EvalCode+0x19)[0x558a2929d289]
python2(+0x12913f)[0x558a292cd13f]
python2(PyRun_FileExFlags+0x82)[0x558a292c8032]
python2(PyRun_SimpleFileExFlags+0x19e)[0x558a292c7b7e]
python2(Py_Main+0x6c2)[0x558a29278a02]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f6b4d2033f1]
python2(_start+0x2a)[0x558a2927822a]

Any Ideas for that?

Greetings,

^.^ Dingo

@petterreinholdtsen
Copy link
Contributor

The message remind me of a crash I saw on Raspian, where something was incorrectly compiled.

I do not see the crash on Debian Buster (amd64), where I have been able to build and run the program, and see a message show up on my pager unit. Because of this, I suspect the problem is not with gr-mixalot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants