Csound Csound-dev Csound-tekno Search About

csdebugger causes segfault

Date2016-04-05 19:18
FromFfanci Silvain
Subjectcsdebugger causes segfault
Hey hey everyone,
csdebugger has repeatedly crashed on me. It runs its first pass. On the second 
pass just after the info "SECTION 1:" it prints:
Csound is already started, call csoundReset()
before starting again
Csound filename: osc.csd
Csound tidy up: Segmentation fault
...

This happened with two different files, that csound will render perfectly 
otherwise. I also tried with the atonek.csd example from the manual.

Why could that happen? Is it not meant for direct execution from the 
commandline?

Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

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

Date2016-04-05 19:41
FromRory Walsh
SubjectRe: csdebugger causes segfault
I think this wrote this example of how one can implement the debugger into an API driven program. I will take a look and see what's going on. Much has changed in the API since I wrote it!  

On 5 April 2016 at 19:18, Ffanci Silvain <silvain@freeshell.de> wrote:
Hey hey everyone,
csdebugger has repeatedly crashed on me. It runs its first pass. On the second pass just after the info "SECTION 1:" it prints:
Csound is already started, call csoundReset()
before starting again
Csound filename: osc.csd
Csound tidy up: Segmentation fault
...

This happened with two different files, that csound will render perfectly otherwise. I also tried with the atonek.csd example from the manual.

Why could that happen? Is it not meant for direct execution from the commandline?

Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

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

Date2016-04-05 20:25
FromFfanci Silvain
SubjectRe: csdebugger causes segfault
Rory Walsh, Apr 5 2016:

> I think this wrote this example of how one can implement the debugger into
> an API driven program. I will take a look and see what's going on. Much has
> changed in the API since I wrote it!
Thank you Rory. Let me know, if I can help some more from the user's perspective.
...

Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

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

Date2016-04-05 22:03
FromRory Walsh
SubjectRe: csdebugger causes segfault
Attachmentsout.gif  
It's working Ok for me. To use it you should pass 3 arguments, the file name, the instr number and the ksmps offset. I just ran it with:

./csdebugger test.csd 1 200

And it hit the break-point in instrument 1 after 200 k-cycles. It printed this once it hit:

Breakpoint at instr 1
Number of k-cycles into performance: 199
------------------------------------------------------ 
VarName:k1 value = 1.07176 varType[k] 
VarName:ksmps Unknown type varType[r] 

But really, this is a very simple example of how to use the debugger. It's not really very useful. If you wish to use the debugger you should probably use it through CsoundQT or Cabbage. Actually, I assume it's in CsoundQT since Andres wrote it, but I can't say for sure. It's definitely available in Cabbage, as the attached screenshot shows. Note that you can only set breakpoints on an instrument, not a line within an instrument. And hitting continue will simply jump to the next k-cycle. 


On 5 April 2016 at 20:25, Ffanci Silvain <silvain@freeshell.de> wrote:
Rory Walsh, Apr 5 2016:

I think this wrote this example of how one can implement the debugger into
an API driven program. I will take a look and see what's going on. Much has
changed in the API since I wrote it!
Thank you Rory. Let me know, if I can help some more from the user's perspective.
...


Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

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

Date2016-04-06 08:57
FromTarmo Johannes
SubjectRe: csdebugger causes segfault

Hi,

 

YEs, there is the debugging mode in CsoundQt but as much I know, both Csound and CsoundQT but be built in debug mode (which the official installers are not). I have tested it lightly but it works ( build qith qmake COFIG+= debugger option)

 

tarmo

 

On Tuesday 05 April 2016 22:03:04 you wrote:

> It's working Ok for me. To use it you should pass 3 arguments, the file

> name, the instr number and the ksmps offset. I just ran it with:

>

> ./csdebugger test.csd 1 200

>

> And it hit the break-point in instrument 1 after 200 k-cycles. It printed

> this once it hit:

>

> Breakpoint at instr 1

> Number of k-cycles into performance: 199

> ------------------------------------------------------

> VarName:k1 value = 1.07176 varType[k]

> VarName:ksmps Unknown type varType[r]

>

> But really, this is a very simple example of how to use the debugger. It's

> not really very useful. If you wish to use the debugger you should probably

> use it through CsoundQT or Cabbage. Actually, I assume it's in CsoundQT

> since Andres wrote it, but I can't say for sure. It's definitely available

> in Cabbage, as the attached screenshot shows. Note that you can only set

> breakpoints on an instrument, not a line within an instrument. And hitting

> continue will simply jump to the next k-cycle.

>

> On 5 April 2016 at 20:25, Ffanci Silvain <silvain@freeshell.de> wrote:

> > Rory Walsh, Apr 5 2016:

> >

> > I think this wrote this example of how one can implement the debugger into

> >

> >> an API driven program. I will take a look and see what's going on. Much

> >> has

> >> changed in the API since I wrote it!

> >

> > Thank you Rory. Let me know, if I can help some more from the user's

> > perspective.

> > ...

> >

> >

> > Ta-ta

> > ----

> > Ffanci

> > * Homepage: https://freeshell.de/~silvain

> > * Twitter: http://twitter.com/ffanci_silvain

> > * GitHub: https://github.com/fsilvain

> >

> > 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

 


Date2016-04-15 00:50
FromAndres Cabrera
SubjectRe: csdebugger causes segfault
Hi Rory,

Cool to see you've integrated the debugger in Cabbage. CsoundQt can also be built with debugger support:

http://csoundqt.github.io/images/CsoundQt090.png

I feel the debugger work is still incomplete, as I am waiting for Steven to complete the work on types. When that is done the debugger can expose very rich and complex data from the running instance.

Cheers,
Andrés

On Tue, Apr 5, 2016 at 2:03 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
It's working Ok for me. To use it you should pass 3 arguments, the file name, the instr number and the ksmps offset. I just ran it with:

./csdebugger test.csd 1 200

And it hit the break-point in instrument 1 after 200 k-cycles. It printed this once it hit:

Breakpoint at instr 1
Number of k-cycles into performance: 199
------------------------------------------------------ 
VarName:k1 value = 1.07176 varType[k] 
VarName:ksmps Unknown type varType[r] 

But really, this is a very simple example of how to use the debugger. It's not really very useful. If you wish to use the debugger you should probably use it through CsoundQT or Cabbage. Actually, I assume it's in CsoundQT since Andres wrote it, but I can't say for sure. It's definitely available in Cabbage, as the attached screenshot shows. Note that you can only set breakpoints on an instrument, not a line within an instrument. And hitting continue will simply jump to the next k-cycle. 


On 5 April 2016 at 20:25, Ffanci Silvain <silvain@freeshell.de> wrote:
Rory Walsh, Apr 5 2016:

I think this wrote this example of how one can implement the debugger into
an API driven program. I will take a look and see what's going on. Much has
changed in the API since I wrote it!
Thank you Rory. Let me know, if I can help some more from the user's perspective.
...


Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

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

Date2016-04-15 08:27
FromRory Walsh
SubjectRe: csdebugger causes segfault

It's been in there since you first released it, and it still works perfectly after all the messing I've done with the Cabbage code base since then ;)

On 15 Apr 2016 12:50 am, "Andres Cabrera" <mantaraya36@gmail.com> wrote:
Hi Rory,

Cool to see you've integrated the debugger in Cabbage. CsoundQt can also be built with debugger support:

http://csoundqt.github.io/images/CsoundQt090.png

I feel the debugger work is still incomplete, as I am waiting for Steven to complete the work on types. When that is done the debugger can expose very rich and complex data from the running instance.

Cheers,
Andrés

On Tue, Apr 5, 2016 at 2:03 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
It's working Ok for me. To use it you should pass 3 arguments, the file name, the instr number and the ksmps offset. I just ran it with:

./csdebugger test.csd 1 200

And it hit the break-point in instrument 1 after 200 k-cycles. It printed this once it hit:

Breakpoint at instr 1
Number of k-cycles into performance: 199
------------------------------------------------------ 
VarName:k1 value = 1.07176 varType[k] 
VarName:ksmps Unknown type varType[r] 

But really, this is a very simple example of how to use the debugger. It's not really very useful. If you wish to use the debugger you should probably use it through CsoundQT or Cabbage. Actually, I assume it's in CsoundQT since Andres wrote it, but I can't say for sure. It's definitely available in Cabbage, as the attached screenshot shows. Note that you can only set breakpoints on an instrument, not a line within an instrument. And hitting continue will simply jump to the next k-cycle. 


On 5 April 2016 at 20:25, Ffanci Silvain <silvain@freeshell.de> wrote:
Rory Walsh, Apr 5 2016:

I think this wrote this example of how one can implement the debugger into
an API driven program. I will take a look and see what's going on. Much has
changed in the API since I wrote it!
Thank you Rory. Let me know, if I can help some more from the user's perspective.
...


Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

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

Date2016-04-15 19:06
FromSteven Yi
SubjectRe: csdebugger causes segfault
Hi Andres,

Are you referring to:

https://github.com/csound/csound/issues/444

for types and channels?

steven



On Thu, Apr 14, 2016 at 7:50 PM, Andres Cabrera  wrote:
> Hi Rory,
>
> Cool to see you've integrated the debugger in Cabbage. CsoundQt can also be
> built with debugger support:
>
> http://csoundqt.github.io/images/CsoundQt090.png
>
> I feel the debugger work is still incomplete, as I am waiting for Steven to
> complete the work on types. When that is done the debugger can expose very
> rich and complex data from the running instance.
>
> Cheers,
> Andrés
>
> On Tue, Apr 5, 2016 at 2:03 PM, Rory Walsh  wrote:
>>
>> It's working Ok for me. To use it you should pass 3 arguments, the file
>> name, the instr number and the ksmps offset. I just ran it with:
>>
>> ./csdebugger test.csd 1 200
>>
>> And it hit the break-point in instrument 1 after 200 k-cycles. It printed
>> this once it hit:
>>
>> Breakpoint at instr 1
>> Number of k-cycles into performance: 199
>> ------------------------------------------------------
>> VarName:k1 value = 1.07176 varType[k]
>> VarName:ksmps Unknown type varType[r]
>>
>> But really, this is a very simple example of how to use the debugger. It's
>> not really very useful. If you wish to use the debugger you should probably
>> use it through CsoundQT or Cabbage. Actually, I assume it's in CsoundQT
>> since Andres wrote it, but I can't say for sure. It's definitely available
>> in Cabbage, as the attached screenshot shows. Note that you can only set
>> breakpoints on an instrument, not a line within an instrument. And hitting
>> continue will simply jump to the next k-cycle.
>>
>>
>> On 5 April 2016 at 20:25, Ffanci Silvain  wrote:
>>>
>>> Rory Walsh, Apr 5 2016:
>>>
>>>> I think this wrote this example of how one can implement the debugger
>>>> into
>>>> an API driven program. I will take a look and see what's going on. Much
>>>> has
>>>> changed in the API since I wrote it!
>>>
>>> Thank you Rory. Let me know, if I can help some more from the user's
>>> perspective.
>>> ...
>>>
>>>
>>> Ta-ta
>>> ----
>>> Ffanci
>>> * Homepage: https://freeshell.de/~silvain
>>> * Twitter:  http://twitter.com/ffanci_silvain
>>> * GitHub:   https://github.com/fsilvain
>>>
>>> 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

Date2016-04-16 01:15
FromAndres Cabrera
SubjectRe: csdebugger causes segfault
Partly, but also internally to have an API to get data from complex types.

Cheers,
Andrés

On Fri, Apr 15, 2016 at 11:06 AM, Steven Yi <stevenyi@gmail.com> wrote:
Hi Andres,

Are you referring to:

https://github.com/csound/csound/issues/444

for types and channels?

steven



On Thu, Apr 14, 2016 at 7:50 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:
> Hi Rory,
>
> Cool to see you've integrated the debugger in Cabbage. CsoundQt can also be
> built with debugger support:
>
> http://csoundqt.github.io/images/CsoundQt090.png
>
> I feel the debugger work is still incomplete, as I am waiting for Steven to
> complete the work on types. When that is done the debugger can expose very
> rich and complex data from the running instance.
>
> Cheers,
> Andrés
>
> On Tue, Apr 5, 2016 at 2:03 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
>>
>> It's working Ok for me. To use it you should pass 3 arguments, the file
>> name, the instr number and the ksmps offset. I just ran it with:
>>
>> ./csdebugger test.csd 1 200
>>
>> And it hit the break-point in instrument 1 after 200 k-cycles. It printed
>> this once it hit:
>>
>> Breakpoint at instr 1
>> Number of k-cycles into performance: 199
>> ------------------------------------------------------
>> VarName:k1 value = 1.07176 varType[k]
>> VarName:ksmps Unknown type varType[r]
>>
>> But really, this is a very simple example of how to use the debugger. It's
>> not really very useful. If you wish to use the debugger you should probably
>> use it through CsoundQT or Cabbage. Actually, I assume it's in CsoundQT
>> since Andres wrote it, but I can't say for sure. It's definitely available
>> in Cabbage, as the attached screenshot shows. Note that you can only set
>> breakpoints on an instrument, not a line within an instrument. And hitting
>> continue will simply jump to the next k-cycle.
>>
>>
>> On 5 April 2016 at 20:25, Ffanci Silvain <silvain@freeshell.de> wrote:
>>>
>>> Rory Walsh, Apr 5 2016:
>>>
>>>> I think this wrote this example of how one can implement the debugger
>>>> into
>>>> an API driven program. I will take a look and see what's going on. Much
>>>> has
>>>> changed in the API since I wrote it!
>>>
>>> Thank you Rory. Let me know, if I can help some more from the user's
>>> perspective.
>>> ...
>>>
>>>
>>> Ta-ta
>>> ----
>>> Ffanci
>>> * Homepage: https://freeshell.de/~silvain
>>> * Twitter:  http://twitter.com/ffanci_silvain
>>> * GitHub:   https://github.com/fsilvain
>>>
>>> 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