[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: qa_qtgui (Failed)-Segmentation fault (core dumped)
From: |
Vasil Velichkov |
Subject: |
Re: qa_qtgui (Failed)-Segmentation fault (core dumped) |
Date: |
Tue, 30 Nov 2021 16:58:36 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 |
Hi Isaac,
On 30/11/2021 16.15, isaac mario tupac davila wrote:
> Thanks for the respond. This is what I see. I had a GR 3.7.13 before. I
> desintaled with make uninstall but I didn't erase its workarea file. This
> could be the problem?...I'm installing this new GNR 3.8.1 in a new worarea
> file by the way.
Which Linux distribution do you use? Why 3.8.1 and not the latest 3.8.4.0?
> ==18632== by 0x544F050: dlopen@@GLIBC_2.2.5 (dlopen.c:87)
> ==18632== by 0x5F88BC: _PyImport_FindSharedFuncptr (in
> /usr/bin/python3.6)
> ==18632== by 0x5FBB27: _PyImport_LoadDynamicModuleWithSpec (in
Your crash looks similar to [1], [2], [3]. In all previously reported such
cases the issue was mixing Qt5 with Qt4 libraries.
Do you have qt4-dev and libqwt-dev packages installed on your system? If you
have them but you don't need them for something else then try removing and then
a clean rebuild (e.g. delete the gnuradio's build directory and start from
scratch)
You may try running the qt test under gdb as well. In the test's shell script
instead of valgrind add the following
gdb --ex run --args /usr/bin/python3 -B
/home/soporte/GR-workarea/gnuradio/gr-qtgui/python/qtgui/qa_qtgui.py
and after it stops take a backtrace by executing `bt` command inside the gdb
shell.
[1] https://github.com/gnuradio/gnuradio/issues/3494
[2] https://github.com/gnuradio/gnuradio/issues/2506
[3] https://github.com/gnuradio/gnuradio/issues/2027
Regards,
Vasil