> On Wed, Feb 26, 2014 at 11:26 PM, West, Nathan <n...@ostatemail.okstate.edu> > wrote: >> >> On Wednesday, February 26, 2014, Tom Rondeau <t...@trondeau.com> wrote: >>> >>> On Wed, Feb 26, 2014 at 12:01 PM, Manu T S <manu.t.s...@gmail.com> wrote: >>> > Hello Everyone, >>> > >>> > Not sure if this is already discussed here. >>> > >>> > I am facing segmentation fault when running benchmark_rx in narrowband >>> > examples. It seems like those example used to work fine before, but now >>> > they >>> > are having these issues. >>> >>> >>> > Manu T S >>> >>> >>> This could be an issue related to the constellation_receiver QA issue >>> a few people have seen lately. I can't replicate it on my end, but >>> Nathan can and is helping to track it down. >>> >>> Tom >>> >>> >> >> That was my first thought as well. At this point we should probably file >> this in the bug tracker. >> >> Manu, >> >> Can you send me a backtrace, your processor type, and compiler >> information? >> >> Nathan > On Wed, Feb 26, 2014 at 12:33 PM, Manu T S <manu.t.s...@gmail.com> wrote: > Hi, > > Thanks for the responses. > > Output to "lscpu", "cat /proc/cpuinfor", "gcc -v", "python" can be found in > the link below: > > http://home.iitb.ac.in/~manu.ts/cpu-info > > I am still figuring out how to get the backtrace. > > -- > Manu T S
$ gdb python # this brings up gdb prompt: (gdb) run benchmark_rx.py -f 900M -m bpsk --rx-gain=25 -r 1M then it will run, probably crash. then enter (gdb) bt Nathan _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio