Dear Bill,
Thanks for the help. Now I also know how to build only wsprd :)
There you go:
(gdb) r
Starting program: /root/wsjtx/build/Debug/wsprd -f 7.0386
wspr_7038600160310_1944.wav
Cannot access memory at address 0x0
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabi/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x0001b4fc in get_wspr_channel_symbols (rawmessage=0x210d8 "I2GPG JN45 33",
hashtab=0xb68e3008 "", symbols=0x0)
at /root/wsjtx/src/lib/wsprd/wsprsim_utils.c:309
309 symbols[i]=2*channelbits[i]+pr3[i];
(gdb) bt
#0 0x0001b4fc in get_wspr_channel_symbols (rawmessage=0x210d8 "I2GPG JN45 33",
hashtab=0xb68e3008 "", symbols=0x0)
at /root/wsjtx/src/lib/wsprd/wsprsim_utils.c:309
#1 0x00018e48 in main (argc=4, argv=0xbefff744) at
/root/wsjtx/src/lib/wsprd/wsprd.c:1088
(gdb)
73 de PA7T / Clemens
Am 14.03.2016 um 17:33 schrieb Bill Somerville <[email protected]>:
> On 14/03/2016 16:19, Clemens Heese wrote:
>> At least I get a segmentation fault with all my wav files, which decode fine
>> on my other machines.
>> Let me know how I can configure a debug build and I will distribute the
>> output.
> Hi Clemens,
>
> assuming you are building WSJT-X using CMake then you will need to
> create a separate build for the debug configuration build. So for
> example if you configured a default release configuration build
> something like:
>
> mkdir -p ~/wsjtx-prefix/build
> cd ~/wsjtx-prefix/build
> cmake ... -D CMAKE-INSTALL_PREFIX=~/wsjtx-prefix ~/wsjtx-prefix/src
> cmake --build . --target install
>
> then to make a debug configuration build you would do the above again
> with the following additions:
>
> mkdir -p ~/wsjtx-prefix/build/Debug
> cd ~/wsjtx-prefix/build/Debug
> cmake ... -D CMAKE_BUILD_TYPE=Debug -D
> CMAKE_INSTALL_PREFIX=~/wsjtx-prefix/Debug ~/wsjtx-prefix/src
> cmake --build . --target wsprd
>
> this will build the wsprd program in a debug configuration located in
> the current directory.
>
> As a first step run the debug version using gdb on the target machine like:
>
> gdb --args wsprd -f 7.0386 wspr_7038600160310_1944.wav
> ...
> (gdb)
>
> start the program with the 'r' command and when the SEGV happens you can
> get a stack backtrace by using the 'bt' command. Send us the output of
> that and I will assess what the best next step is.
>
> 73
> Bill
> G4WJS.
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
> _______________________________________________
> wsjt-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
