Gqrx 2.2 OSX build crashes when invoked from the command-line with "-h"

[Alexander Janssen]

Hi there again,

following the instructions from README-mac.txt I tried to invoke Gqrx with the -h parameter from the commandline which lead to a crash:

$ pwd

/Applications

$ Gqrx.app/Contents/MacOS/Gqrx -h

dyld: Symbol not found: _volk_32u_byteswap_u

  Referenced from: /Applications/Gqrx.app/Contents/MacOS/../Frameworks/libgnuradio-blocks.3.7.0.dylib

  Expected in: /Users/ajanssen/gnuradio/lib/libvolk.0.0.0.dylib

 in /Applications/Gqrx.app/Contents/MacOS/../Frameworks/libgnuradio-blocks.3.7.0.dylib

Trace/BPT trap: 5

The directory from where Gqrx is invoked doesn't really matter though.

Stacktrace in Google Drive: https://drive.google.com/file/d/0B9A5hQIGGwplSmlJVjhRWm12bDA/edit?usp=sharing

Thanks, Alex.

P.S.: Yes, I know it's considered beta-software, just trying to be helpful. Also: Is it better to submit crash reports at Github or here?

[Alexander Janssen]

Never mind. I had another installation of gnuradio in my $HOME which was compiled with totally different patches, is another version and a totally different platform anyway. Gqrx preferred these libs instead of it's own - my fault.

Alex.

[Alexandru Csete]

On Sat, Dec 7, 2013 at 7:45 PM, Alexander Janssen
<alexande...@gmail.com> wrote:
> Hi there again,
>
> following the instructions from README-mac.txt I tried to invoke Gqrx with
> the -h parameter from the commandline which lead to a crash:
>
> $ pwd
> /Applications
> $ Gqrx.app/Contents/MacOS/Gqrx -h
> dyld: Symbol not found: _volk_32u_byteswap_u
> Referenced from:
> /Applications/Gqrx.app/Contents/MacOS/../Frameworks/libgnuradio-blocks.3.7.0.dylib
> Expected in: /Users/ajanssen/gnuradio/lib/libvolk.0.0.0.dylib
> in
> /Applications/Gqrx.app/Contents/MacOS/../Frameworks/libgnuradio-blocks.3.7.0.dylib
> Trace/BPT trap: 5

It seems that you have some additional gnuradio installed in
/Users/ajanssen/gnuradio ???
When you try to run gqrx from the command line it picks up libvolk
from that directory and it is probably an old version. You should
disable it.

> P.S.: Yes, I know it's considered beta-software, just trying to be helpful.
> Also: Is it better to submit crash reports at Github or here?

Well, we must eliminate all the bugs so just keep
Eventually, any issue that needs a non-trivial action must end up in
github otherwise I will most certainly forget about it. But if you
prefer the mailing list, it's fine.

Alex