From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-hams@vger.kernel.org
Subject: Re: PROBLEM: gMFSK v0.5 locks up.
Date: Sat, 12 Jul 2003 18:13:21 +1000 [thread overview]
Message-ID: <20030712081321.GA4419@cloud.net.au> (raw)
In-Reply-To: <3F0FC0FD.5060307@pi8zaa.ampr.org>
On Sat, Jul 12, 2003 at 10:04:13AM +0200, Arno Verhoeven wrote:
> Now that I've got gmfsk to compile, I run into another problem.
>
> Until now I didn't get it to produce any sound yet. (sound works on that
> system. Other applications can use the sound card)
>
> There are 2 ways that I can make gmfsk lock up.
>
> 1. click the "Abort transmission immediately" button.
> 2. click the "Mode" pull-down menu and try to select another mode.
>
> There are no messages in /var/log/syslog and /var/log/messages
> I'm using fftw-2.1.5, kernel 2.4.21 glibc-2.3.1 and all were compiled
> with gcc-3.2.3.
In what way does it lock up? Just the program hangs or all X programs or
your whole system?
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2003-07-12 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 18:58 ANNOUNCE: gMFSK v0.5 Tomi Manninen
2003-04-20 2:37 ` Hamish Moffatt
2003-04-20 9:32 ` Gérard Parat / F6FGZ
2003-07-11 20:29 ` Arno Verhoeven
2003-07-11 21:11 ` Tomi Manninen
2003-07-12 10:40 ` Wilbert Knol
2003-07-11 21:25 ` Aleksandar Ilic
2003-07-11 21:50 ` Arno Verhoeven
2003-07-12 8:04 ` PROBLEM: gMFSK v0.5 locks up Arno Verhoeven
2003-07-12 8:13 ` Hamish Moffatt [this message]
2003-07-12 15:07 ` Arno Verhoeven
2003-07-12 15:12 ` Edson Pereira
2003-09-11 7:51 ` SOLVED (Re: PROBLEM: gMFSK v0.5 locks up.) Arno Verhoeven
2003-07-12 16:30 ` PROBLEM: gMFSK v0.5 locks up Tomi Manninen
2003-07-13 20:15 ` Arno Verhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030712081321.GA4419@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.