On 15/03/2016 10:31, Clemens Heese wrote: > (gdb) r > Starting program: /root/src/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". > > Breakpoint 1, get_wspr_channel_symbols (rawmessage=0x210d8 "I2GPG JN45 33", > hashtab=0xb68dc008 "", symbols=0xbeff9050 "") at > /root/src/wsjtx/src/lib/wsprd/wsprsim_utils.c:167 > 167 int m=0, n=0, ntype=0; > (gdb) c > Continuing. > > Program received signal SIGSEGV, Segmentation fault. > 0x0001b4fc in get_wspr_channel_symbols (rawmessage=0x210d8 "I2GPG JN45 33", > hashtab=0xb68dc008 "", symbols=0x0) at > /root/src/wsjtx/src/lib/wsprd/wsprsim_utils.c:309 HI Clemens,
ok so the SEGV is on the first call to get_wspr_channel_symbols() and the 'symbols' pointer is ok at the start of the function, so something in the function or what it calls is corrupting the symbols variable. Most likely is a bounds error on an array somewhere although the issue only happening on ARM must also be a factor. One thing we can try is to set a gdb watch on the symbols variable, this doesn't always work but is worth a try. To do this run the same as the last test but after the breakpoint is hit but before using the 'c' command to continue type: watch symbols and report back what happens. 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
