[iiwusynth-devel] RE: [Swami-devel] iiwusynth segfault

[Mark Knecht]

Peter,
   I am on the Planet CCRMA flow. In this installation, it's Redhat 7.3, but
we have access to an application called jackstart, which allows user
accounts to run jackd but get real-time scheduling. This works with Ardour,
as well as other jack apps as far as I can tell. On one machine with a SB
Audigy card it works fine with iiwusynth. It fails this way on my main DAW
box. I will try running iiwusynth as root just for a test, but I do not have
to do that with other apps using this flow.

   All my machines (5 PCs right now) are Athlons using this flow. The
machine that fails is an Athlon XP and has a new RME HDSP 9652 sound card in
it, but other than that it's pretty much the same as the others which are
Athlon with various sound cards.

   Let me know if you want more info. I'll drop you a note in a few hours
when I get to do the root experiment.

   I can also use jackd as root and try that to see if iiwusynth works with
the standard Jack, but may have uncovered a problem with jackstart. We'll
see.

Thanks,
Mark



> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden Behalf Of Peter
> Hanappe
> Sent: Thursday, January 23, 2003 3:10 PM
> To: Mark Knecht; iiwusynth-devel; address@hidden
> Subject: Re: [Swami-devel] iiwusynth segfault
>
>
>
> Hi Mark,
>
> I've only scanned very quickly through today's messages (it's been a
> long day) so I didn't analyze the problem in detail.
> Just one quick hint: the Jack server
> requires Jack'ed applications to run with root privileges since Jack
> uses real-time scheduling. So currently you have to start iiwusynth
> as root. Also the -z and -c options (as in iiwusynth -a jack -z
> 1024 -c 2) are ignored when using the Jack driver since the period size
> and period count are set when you start the jackd daemon.
>
> BTW: I will be gone till next thursday so I won't be able to dig
> into the problem till then.
>
> Best,
> Peter
>
>
>
> Mark Knecht wrote:
> > On Thu, 2003-01-23 at 06:36, Josh Green wrote:
> >
> >
> >>P.S. Something else to make sure of is that you don't have any old
> >>versions of libiiwusynth.so.* hanging around. This can cause lots of
> >>weired problems.
> >>
> >>
> >
> > How do I look around for this file? Is there a specific path it would be
> > at?
> >
> > I'm have tried all of the ideas you had, but none of them are creating a
> > segfault inside of gdb.
> >
> > I am able to capture a core dump when I run iiwusynth -a jack outside of
> > gdb. Is that worth anything without the back trace fom gdb?
> >
> > Thanks,
> > Mark
> >
> >
> >
> > -------------------------------------------------------
> > This SF.NET email is sponsored by:
> > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> > http://www.vasoftware.com
> > _______________________________________________
> > Swami-devel mailing list
> > address@hidden
> > https://lists.sourceforge.net/lists/listinfo/swami-devel
>
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Swami-devel mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/swami-devel
>
>