On 22/11/11 10:21 PM, Matt Mills wrote: > > > On Tue, Nov 22, 2011 at 11:28 AM, Philip Balister <[email protected] > <mailto:[email protected]>> wrote: > > You can use the single threaded scheduler by setting an environment > variable: > > export GR_SCHEDULER=STS > > > > Gave this a shot; app runs for a while (at 100% CPU with quite a few > overruns) then segfaults... > [20077.594080] python[16760]: segfault at 8 ip b7478dc4 sp a862c09c > error 6 in libc-2.11.1.so <http://libc-2.11.1.so>[b741c000+153000] > and > [21548.361453] python[15672]: segfault at 0 ip b74b9330 sp a9b6f0e0 > error 4 in libc-2.11.1.so <http://libc-2.11.1.so>[b745a000+153000] > The SegFaults are discouraging--it means there's a bug in one of the blocks you're using, or the Gnu Radio scheduler/data-shuffler. It's a big flow-graph (you'd mentioned 197 blocks), so it will be a pain to whittle down exactly *which* block is causing the segfault--and it's provoking it from inside libc, which makes it even less fun.
The overruns aren't a big surprise, given that you were having *some* with TPB scheduling (and thus using both your CPU cores), with STS, you're running all on a single CPU. -- Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
