On 05/31/2010 12:58 AM, Eric Blossom wrote:
>
> When it wedges, does it continue to consume CPU, or does it appear to
> be blocked?
>
>
Looks like it continues to consume cpu, but at a lower rate than "normal".
> When it wedges, you should be able to attach to it with gdb.
> Run gdb on /usr/bin
On 05/31/2010 12:58 AM, Eric Blossom wrote:
>
> When it wedges, does it continue to consume CPU, or does it appear to
> be blocked?
>
Oooh, I forgot to check that, but clearly another clue that needs to be
gathered!
> When it wedges, you should be able to attach to it with gdb.
> Run gdb on /usr
On Sun, May 30, 2010 at 11:26:34PM -0400, Marcus D. Leech wrote:
> I have a long-running Gnu Radio application--my VLF sid receiver. It
> seems to "wedge" after a few days
> of flawless operation.
>
> The application uses an audio source, and an audio sink, but usually the
> source and sink are
I have a long-running Gnu Radio application--my VLF sid receiver. It
seems to "wedge" after a few days
of flawless operation.
The application uses an audio source, and an audio sink, but usually the
source and sink are on
two different sound cards.
The application uses a number of WxGUI widg
