[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Gnuradio locking up

From: Marcus D. Leech
Subject: Re: [Discuss-gnuradio] Gnuradio locking up
Date: Tue, 22 Nov 2011 22:30:36 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20101027 Fedora/3.0.10-1.fc12 Thunderbird/3.0.10

On 22/11/11 10:21 PM, Matt Mills wrote:

On Tue, Nov 22, 2011 at 11:28 AM, Philip Balister <address@hidden> wrote:
You can use the single threaded scheduler by setting an environment


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[b741c000+153000]
[21548.361453] python[15672]: segfault at 0 ip b74b9330 sp a9b6f0e0 error 4 in 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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]