To use WinCVS you need a digital certificate and the PuTTY program, which
WinCVS uses for secure shell (SSH) authentication to CVS. You are trying to
use password authentication, which won't work in WinCVS.There are detailed
instructions for getting this set up on SourceForge.

If you install Cygwin, which comes with SSH and CVS, you can use password
authentication just fine. If you have room on your PC you will find
installing and using Cygwin (with command-line use of CVS) easier to get
going with than WinCVS.

----- Original Message ----- 
From: "Andres Cabrera" 
To: "Csound Developers Discussion List" 
Sent: Wednesday, July 14, 2004 8:23 PM
Subject: [CSOUND-DEV:4981] can't write to cvs


> Hi John,
>
> I can't seem to write to the cvs repository,  can you check if
> permissions for me are set correctly? I get the following from cvs:
>
> cvs -d :pserver:mantaraya36@cvs.sourceforge.net:/cvsroot/csound login
> Logging in to
:pserver:mantaraya36@cvs.sourceforge.net:2401:/cvsroot/csound
>
> ***** CVS exited normally with code 0 *****
>
> cvs commit -m "Added vstbload-not yet working. fixed vstinfo to work
> when not called at initial..." vst4cs.cpp vst4cs.h (in directory
> H:\C_Progs\csound5\Opcodes\vst4cs\src)
> cvs [server aborted]: "commit" requires write access to the repository
>
> ***** CVS exited normally with code 1 *****
>
> It's very probable I'm doing something wrong. Does anyone know if you
> have to do anything different when using winCVS?
>
> Cheers,
> Andrés
>
>

Hi Andres,

Just a clarification of Michael's comments, it means you need to use the
ext protocol to access the cvs, which requires ssh.  If using from the
commandline, you wouldn't have to do a login with ext as it does it
every connection.  So your commandline would be like:

cvs -d:ext:mantaraya36@cvs.sourceforge.net:/cvsroot csound commit -m
"Added vstbload-not yet working. fixed vstinfo to work
when not called at initial..." vst4cs.cpp vst4cs.h

If you don't generate a ssh key, then this commandline would then come
up with a prompt to ask you your password.  If you do use a key, then
it'll use that and won't ask you anything.

steven


On Wed, 2004-07-14 at 18:51, Michael Gogins wrote:
> To use WinCVS you need a digital certificate and the PuTTY program, which
> WinCVS uses for secure shell (SSH) authentication to CVS. You are trying to
> use password authentication, which won't work in WinCVS.There are detailed
> instructions for getting this set up on SourceForge.
> 
> If you install Cygwin, which comes with SSH and CVS, you can use password
> authentication just fine. If you have room on your PC you will find
> installing and using Cygwin (with command-line use of CVS) easier to get
> going with than WinCVS.
> 
> ----- Original Message ----- 
> From: "Andres Cabrera" 
> To: "Csound Developers Discussion List" 
> Sent: Wednesday, July 14, 2004 8:23 PM
> Subject: [CSOUND-DEV:4981] can't write to cvs
> 
> 
> > Hi John,
> >
> > I can't seem to write to the cvs repository,  can you check if
> > permissions for me are set correctly? I get the following from cvs:
> >
> > cvs -d :pserver:mantaraya36@cvs.sourceforge.net:/cvsroot/csound login
> > Logging in to
> :pserver:mantaraya36@cvs.sourceforge.net:2401:/cvsroot/csound
> >
> > ***** CVS exited normally with code 0 *****
> >
> > cvs commit -m "Added vstbload-not yet working. fixed vstinfo to work
> > when not called at initial..." vst4cs.cpp vst4cs.h (in directory
> > H:\C_Progs\csound5\Opcodes\vst4cs\src)
> > cvs [server aborted]: "commit" requires write access to the repository
> >
> > ***** CVS exited normally with code 1 *****
> >
> > It's very probable I'm doing something wrong. Does anyone know if you
> > have to do anything different when using winCVS?
> >
> > Cheers,
> > Andrés
> >
> >
> 
> 

Hi all,

I'm running gdb and csound seems to segfault when I get to csoundYield
in Top/csound.c:914, at:

return csoundYieldCallback_(csound);

The signal I got was a SIGSEGV.  I'm not sure what's going on here,
maybe the callback didn't get set before returning it?  Any ideas on
what could be happening would be greatly appreciated!

steven

Sorry, never mind.  I traced it a bit further and got:

Breakpoint 1, POLL_EVENTS () at InOut/FL_graph.cpp:284
284             Fl::lock();
Current language:  auto; currently c++
(gdb) n
Warning:
Cannot insert breakpoint 0.
Error accessing memory address 0x0: Input/output error.


I think my version of FLTK is not built with threading and so after
compiling without FLTK things are running just fine.  

I think I figured out something more on testing values from
commonEnvironment['valueName'] that I think will be helpful to know.  It
seems that for values passed in from the command-line, the value in
commonEnvironment will be set as strings.  So, if you did:

scons foo=1 

and in the SConstruct file it was set to:

if commonEnvironment['foo'] == 1:
	...

the test would fail as foo is set to "1" and not 1.  In the SConstruct
file in the opts section, if you set something to 0 as default and are
testing for 1 and pass in foo=1 on the command-line, you might not get
the expected behavior.

Thanks,
steven




On Wed, 2004-07-14 at 21:26, stevenyi wrote:
> Hi all,
> 
> I'm running gdb and csound seems to segfault when I get to csoundYield
> in Top/csound.c:914, at:
> 
> return csoundYieldCallback_(csound);
> 
> The signal I got was a SIGSEGV.  I'm not sure what's going on here,
> maybe the callback didn't get set before returning it?  Any ideas on
> what could be happening would be greatly appreciated!
> 
> steven
> 
>