This is csound 6.07 on OS X. In a simple csd, when (in this case) there 
is an invalid table number, csound cannot be interrupted by ctrl c, or 
killed via the Activity monitor. Also, the CPU is 100 % then and it can 
only be killed with: sudo kill -9 

INIT ERROR in instr 1: Invalid ftable no. 2.000000
asig    fmrhode    .5    kfreq    kc1    kc2    kvdepth kvrate    -1    
-1    -1    ifn4    -1
PERF ERROR in instr 1: No table for FM4Op
    note aborted
       B  3.000 - note deleted.  i1 had 1 init errors

csound command: Segmentation fault
^C
csound command: Interrupt
^C
csound command: Interrupt


Richard

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I think it depends on the segfault. I've had cases like that many times, but not always

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 25 Jun 2016, at 18:32, Richard  wrote:
> 
> This is csound 6.07 on OS X. In a simple csd, when (in this case) there is an invalid table number, csound cannot be interrupted by ctrl c, or killed via the Activity monitor. Also, the CPU is 100 % then and it can only be killed with: sudo kill -9 
> 
> INIT ERROR in instr 1: Invalid ftable no. 2.000000
> asig    fmrhode    .5    kfreq    kc1    kc2    kvdepth kvrate    -1    -1    -1    ifn4    -1
> PERF ERROR in instr 1: No table for FM4Op
>   note aborted
>      B  3.000 - note deleted.  i1 had 1 init errors
> 
> csound command: Segmentation fault
> ^C
> csound command: Interrupt
> ^C
> csound command: Interrupt
> 
> 
> Richard
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>       https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I've had this happen to me before and it seems like a bad condition we
need to fix.  In the interim, instead of using SIGINT (ctrl-c), you
might try SIGQUIT (ctrl-\). I seemed to remember that or some other
keyboard shortcut did the job where ctrl-c did not.

On Sat, Jun 25, 2016 at 1:59 PM, Victor Lazzarini
 wrote:
> I think it depends on the segfault. I've had cases like that many times, but not always
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 25 Jun 2016, at 18:32, Richard  wrote:
>>
>> This is csound 6.07 on OS X. In a simple csd, when (in this case) there is an invalid table number, csound cannot be interrupted by ctrl c, or killed via the Activity monitor. Also, the CPU is 100 % then and it can only be killed with: sudo kill -9 
>>
>> INIT ERROR in instr 1: Invalid ftable no. 2.000000
>> asig    fmrhode    .5    kfreq    kc1    kc2    kvdepth kvrate    -1    -1    -1    ifn4    -1
>> PERF ERROR in instr 1: No table for FM4Op
>>   note aborted
>>      B  3.000 - note deleted.  i1 had 1 init errors
>>
>> csound command: Segmentation fault
>> ^C
>> csound command: Interrupt
>> ^C
>> csound command: Interrupt
>>
>>
>> Richard
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>       https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I had this happen too... I only had one term open at the time, so I
stopped the job (ctrl-z) and then killed the job with SIGKILL (kill -9
%1, assuming this was the only active job in the session... otherwise
%1 might be different).

Not ideal, but it seemed to do the trick for me.

On Wed, Jun 29, 2016 at 2:57 PM, Steven Yi  wrote:
> I've had this happen to me before and it seems like a bad condition we
> need to fix.  In the interim, instead of using SIGINT (ctrl-c), you
> might try SIGQUIT (ctrl-\). I seemed to remember that or some other
> keyboard shortcut did the job where ctrl-c did not.
>
> On Sat, Jun 25, 2016 at 1:59 PM, Victor Lazzarini
>  wrote:
>> I think it depends on the segfault. I've had cases like that many times, but not always
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>>> On 25 Jun 2016, at 18:32, Richard  wrote:
>>>
>>> This is csound 6.07 on OS X. In a simple csd, when (in this case) there is an invalid table number, csound cannot be interrupted by ctrl c, or killed via the Activity monitor. Also, the CPU is 100 % then and it can only be killed with: sudo kill -9 
>>>
>>> INIT ERROR in instr 1: Invalid ftable no. 2.000000
>>> asig    fmrhode    .5    kfreq    kc1    kc2    kvdepth kvrate    -1    -1    -1    ifn4    -1
>>> PERF ERROR in instr 1: No table for FM4Op
>>>   note aborted
>>>      B  3.000 - note deleted.  i1 had 1 init errors
>>>
>>> csound command: Segmentation fault
>>> ^C
>>> csound command: Interrupt
>>> ^C
>>> csound command: Interrupt
>>>
>>>
>>> Richard
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Richard: Could you post a CSD that causes the problem?  We should
diagnose and see what is going on .

On Wed, Jun 29, 2016 at 3:06 PM, Kevin Welsh  wrote:
> I had this happen too... I only had one term open at the time, so I
> stopped the job (ctrl-z) and then killed the job with SIGKILL (kill -9
> %1, assuming this was the only active job in the session... otherwise
> %1 might be different).
>
> Not ideal, but it seemed to do the trick for me.
>
> On Wed, Jun 29, 2016 at 2:57 PM, Steven Yi  wrote:
>> I've had this happen to me before and it seems like a bad condition we
>> need to fix.  In the interim, instead of using SIGINT (ctrl-c), you
>> might try SIGQUIT (ctrl-\). I seemed to remember that or some other
>> keyboard shortcut did the job where ctrl-c did not.
>>
>> On Sat, Jun 25, 2016 at 1:59 PM, Victor Lazzarini
>>  wrote:
>>> I think it depends on the segfault. I've had cases like that many times, but not always
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>>> On 25 Jun 2016, at 18:32, Richard  wrote:
>>>>
>>>> This is csound 6.07 on OS X. In a simple csd, when (in this case) there is an invalid table number, csound cannot be interrupted by ctrl c, or killed via the Activity monitor. Also, the CPU is 100 % then and it can only be killed with: sudo kill -9 
>>>>
>>>> INIT ERROR in instr 1: Invalid ftable no. 2.000000
>>>> asig    fmrhode    .5    kfreq    kc1    kc2    kvdepth kvrate    -1    -1    -1    ifn4    -1
>>>> PERF ERROR in instr 1: No table for FM4Op
>>>>   note aborted
>>>>      B  3.000 - note deleted.  i1 had 1 init errors
>>>>
>>>> csound command: Segmentation fault
>>>> ^C
>>>> csound command: Interrupt
>>>> ^C
>>>> csound command: Interrupt
>>>>
>>>>
>>>> Richard
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>       https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I experience this happen when I try to compile the vcomb manual example.

Csound version 6.07 (double samples) Apr  1 2016
OSX 10.11.5

I attached the .csd just in case my version is stale... my manual and
examples are a year or so old.


On Wed, Jun 29, 2016 at 3:19 PM, Steven Yi  wrote:
> Richard: Could you post a CSD that causes the problem?  We should
> diagnose and see what is going on .
>
> On Wed, Jun 29, 2016 at 3:06 PM, Kevin Welsh  wrote:
>> I had this happen too... I only had one term open at the time, so I
>> stopped the job (ctrl-z) and then killed the job with SIGKILL (kill -9
>> %1, assuming this was the only active job in the session... otherwise
>> %1 might be different).
>>
>> Not ideal, but it seemed to do the trick for me.
>>
>> On Wed, Jun 29, 2016 at 2:57 PM, Steven Yi  wrote:
>>> I've had this happen to me before and it seems like a bad condition we
>>> need to fix.  In the interim, instead of using SIGINT (ctrl-c), you
>>> might try SIGQUIT (ctrl-\). I seemed to remember that or some other
>>> keyboard shortcut did the job where ctrl-c did not.
>>>
>>> On Sat, Jun 25, 2016 at 1:59 PM, Victor Lazzarini
>>>  wrote:
>>>> I think it depends on the segfault. I've had cases like that many times, but not always
>>>>
>>>> Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>> Maynooth University
>>>> Ireland
>>>>
>>>>> On 25 Jun 2016, at 18:32, Richard  wrote:
>>>>>
>>>>> This is csound 6.07 on OS X. In a simple csd, when (in this case) there is an invalid table number, csound cannot be interrupted by ctrl c, or killed via the Activity monitor. Also, the CPU is 100 % then and it can only be killed with: sudo kill -9 
>>>>>
>>>>> INIT ERROR in instr 1: Invalid ftable no. 2.000000
>>>>> asig    fmrhode    .5    kfreq    kc1    kc2    kvdepth kvrate    -1    -1    -1    ifn4    -1
>>>>> PERF ERROR in instr 1: No table for FM4Op
>>>>>   note aborted
>>>>>      B  3.000 - note deleted.  i1 had 1 init errors
>>>>>
>>>>> csound command: Segmentation fault
>>>>> ^C
>>>>> csound command: Interrupt
>>>>> ^C
>>>>> csound command: Interrupt
>>>>>
>>>>>
>>>>> Richard
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>       https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Ok, ctrl-\ seems to work. I did not not this command.

Here is the attached csd, it is the fmrhodes example. The segfault 
occurs simply by the line:

; audio file.
f 2 0 256 1 "./samples/fwavblnk.aiff" 0 0 0

when the path is wrong.

(BTW, maybe we should save these test cases, in case we ever go to a 
system of automated regression testing...
Has this been tested (was there a test case for it? - the case is: 
provide a wrong input for the fgen 2)
If there was no case for it, convert this bug into a test case and add 
it to the list of testcases (ideally a database)
)

Richard


On 29/06/16 20:57, Steven Yi wrote:
> I've had this happen to me before and it seems like a bad condition we
> need to fix.  In the interim, instead of using SIGINT (ctrl-c), you
> might try SIGQUIT (ctrl-\). I seemed to remember that or some other
> keyboard shortcut did the job where ctrl-c did not.
>
> On Sat, Jun 25, 2016 at 1:59 PM, Victor Lazzarini
>  wrote:
>> I think it depends on the segfault. I've had cases like that many times, but not always
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>>> On 25 Jun 2016, at 18:32, Richard  wrote:
>>>
>>> This is csound 6.07 on OS X. In a simple csd, when (in this case) there is an invalid table number, csound cannot be interrupted by ctrl c, or killed via the Activity monitor. Also, the CPU is 100 % then and it can only be killed with: sudo kill -9 
>>>
>>> INIT ERROR in instr 1: Invalid ftable no. 2.000000
>>> asig    fmrhode    .5    kfreq    kc1    kc2    kvdepth kvrate    -1    -1    -1    ifn4    -1
>>> PERF ERROR in instr 1: No table for FM4Op
>>>    note aborted
>>>       B  3.000 - note deleted.  i1 had 1 init errors
>>>
>>> csound command: Segmentation fault
>>> ^C
>>> csound command: Interrupt
>>> ^C
>>> csound command: Interrupt
>>>
>>>
>>> Richard
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here


Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

We do use a test suite already and it should be updated when new issues arise.

Thanks for the test files Richard and Kevin.  We'll have to see what's
going on now.

On Thu, Jun 30, 2016 at 3:21 AM, Richard  wrote:
> Ok, ctrl-\ seems to work. I did not not this command.
>
> Here is the attached csd, it is the fmrhodes example. The segfault occurs
> simply by the line:
>
> ; audio file.
> f 2 0 256 1 "./samples/fwavblnk.aiff" 0 0 0
>
> when the path is wrong.
>
> (BTW, maybe we should save these test cases, in case we ever go to a system
> of automated regression testing...
> Has this been tested (was there a test case for it? - the case is: provide a
> wrong input for the fgen 2)
> If there was no case for it, convert this bug into a test case and add it to
> the list of testcases (ideally a database)
> )
>
> Richard
>
>
>
> On 29/06/16 20:57, Steven Yi wrote:
>>
>> I've had this happen to me before and it seems like a bad condition we
>> need to fix.  In the interim, instead of using SIGINT (ctrl-c), you
>> might try SIGQUIT (ctrl-\). I seemed to remember that or some other
>> keyboard shortcut did the job where ctrl-c did not.
>>
>> On Sat, Jun 25, 2016 at 1:59 PM, Victor Lazzarini
>>  wrote:
>>>
>>> I think it depends on the segfault. I've had cases like that many times,
>>> but not always
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>>> On 25 Jun 2016, at 18:32, Richard  wrote:
>>>>
>>>> This is csound 6.07 on OS X. In a simple csd, when (in this case) there
>>>> is an invalid table number, csound cannot be interrupted by ctrl c, or
>>>> killed via the Activity monitor. Also, the CPU is 100 % then and it can only
>>>> be killed with: sudo kill -9 
>>>>
>>>> INIT ERROR in instr 1: Invalid ftable no. 2.000000
>>>> asig    fmrhode    .5    kfreq    kc1    kc2    kvdepth kvrate    -1
>>>> -1    -1    ifn4    -1
>>>> PERF ERROR in instr 1: No table for FM4Op
>>>>    note aborted
>>>>       B  3.000 - note deleted.  i1 had 1 init errors
>>>>
>>>> csound command: Segmentation fault
>>>> ^C
>>>> csound command: Interrupt
>>>> ^C
>>>> csound command: Interrupt
>>>>
>>>>
>>>> Richard
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>        https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>          https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here