(gdb) backtrace
#0  0x000953a2 in ?? ()
#1  0x00086f2f in ?? ()
#2  0x00079477 in ?? ()
#3  0x0007d07d in ?? ()
#4  0x000879ee in ?? ()
#5  0x97013155 in _pthread_start ()
#6  0x97013012 in thread_start ()

This is from a crash using a simple CSD with -d  -otest.wav  -M0 and  
portmidi, with the following program:

#include 
#include 
#include 
#include 

int main(int argc, char **argv){

   Csound *cs;

   for (int i =0; i < 5; i++) {
     fprintf(stdout, "=========== PLAY TIME %d ===========\n", i+1);
   cs = new Csound();
   cs->Compile(argc, argv);
   cs->Perform();
   delete cs;
   }
   return 0;
}

Why is pthread_start() being called? This should be single-thread.  
What's this thread being started and crashing? Can anyone explain? Is  
that outside Csound?

Victor 

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

This is hard to tell as the symbols are obfuscated.  Did you compile
with noDebug=0 ? If you did, then I'd guess it's happening in a
library used from csound that is not compiled with debug on.

On Mon, Mar 1, 2010 at 1:39 PM, Victor Lazzarini
 wrote:
> (gdb) backtrace
> #0  0x000953a2 in ?? ()
> #1  0x00086f2f in ?? ()
> #2  0x00079477 in ?? ()
> #3  0x0007d07d in ?? ()
> #4  0x000879ee in ?? ()
> #5  0x97013155 in _pthread_start ()
> #6  0x97013012 in thread_start ()
>
> This is from a crash using a simple CSD with -d  -otest.wav  -M0 and
> portmidi, with the following program:
>
> #include 
> #include 
> #include 
> #include 
>
> int main(int argc, char **argv){
>
>   Csound *cs;
>
>   for (int i =0; i < 5; i++) {
>     fprintf(stdout, "=========== PLAY TIME %d ===========\n", i+1);
>   cs = new Csound();
>   cs->Compile(argc, argv);
>   cs->Perform();
>   delete cs;
>   }
>   return 0;
> }
>
> Why is pthread_start() being called? This should be single-thread.
> What's this thread being started and crashing? Can anyone explain? Is
> that outside Csound?
>
> Victor
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

It is probably happening within some library. Does the PortMidi
library use threads now?

Regards,
Mike


On Mon, Mar 1, 2010 at 2:00 PM, Steven Yi  wrote:
> This is hard to tell as the symbols are obfuscated.  Did you compile
> with noDebug=0 ? If you did, then I'd guess it's happening in a
> library used from csound that is not compiled with debug on.
>
> On Mon, Mar 1, 2010 at 1:39 PM, Victor Lazzarini
>  wrote:
>> (gdb) backtrace
>> #0  0x000953a2 in ?? ()
>> #1  0x00086f2f in ?? ()
>> #2  0x00079477 in ?? ()
>> #3  0x0007d07d in ?? ()
>> #4  0x000879ee in ?? ()
>> #5  0x97013155 in _pthread_start ()
>> #6  0x97013012 in thread_start ()
>>
>> This is from a crash using a simple CSD with -d  -otest.wav  -M0 and
>> portmidi, with the following program:
>>
>> #include 
>> #include 
>> #include 
>> #include 
>>
>> int main(int argc, char **argv){
>>
>>   Csound *cs;
>>
>>   for (int i =0; i < 5; i++) {
>>     fprintf(stdout, "=========== PLAY TIME %d ===========\n", i+1);
>>   cs = new Csound();
>>   cs->Compile(argc, argv);
>>   cs->Perform();
>>   delete cs;
>>   }
>>   return 0;
>> }
>>
>> Why is pthread_start() being called? This should be single-thread.
>> What's this thread being started and crashing? Can anyone explain? Is
>> that outside Csound?
>>
>> Victor
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I don't know. But the funny thing is: if I set a breakpoint in  
csoundReset, the crash seems to happen in
csound->spoutran().

Victor


On 1 Mar 2010, at 19:32, Michael Gogins wrote:

> It is probably happening within some library. Does the PortMidi
> library use threads now?
>
> Regards,
> Mike
>
>
> On Mon, Mar 1, 2010 at 2:00 PM, Steven Yi  wrote:
>> This is hard to tell as the symbols are obfuscated.  Did you compile
>> with noDebug=0 ? If you did, then I'd guess it's happening in a
>> library used from csound that is not compiled with debug on.
>>
>> On Mon, Mar 1, 2010 at 1:39 PM, Victor Lazzarini
>>  wrote:
>>> (gdb) backtrace
>>> #0  0x000953a2 in ?? ()
>>> #1  0x00086f2f in ?? ()
>>> #2  0x00079477 in ?? ()
>>> #3  0x0007d07d in ?? ()
>>> #4  0x000879ee in ?? ()
>>> #5  0x97013155 in _pthread_start ()
>>> #6  0x97013012 in thread_start ()
>>>
>>> This is from a crash using a simple CSD with -d  -otest.wav  -M0 and
>>> portmidi, with the following program:
>>>
>>> #include 
>>> #include 
>>> #include 
>>> #include 
>>>
>>> int main(int argc, char **argv){
>>>
>>>   Csound *cs;
>>>
>>>   for (int i =0; i < 5; i++) {
>>>     fprintf(stdout, "=========== PLAY TIME %d ===========\n", i+1);
>>>   cs = new Csound();
>>>   cs->Compile(argc, argv);
>>>   cs->Perform();
>>>   delete cs;
>>>   }
>>>   return 0;
>>> }
>>>
>>> Why is pthread_start() being called? This should be single-thread.
>>> What's this thread being started and crashing? Can anyone explain?  
>>> Is
>>> that outside Csound?
>>>
>>> Victor
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> -- 
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Victor,

Just had a thought, does this fail before compilation, during
performance, or after performance?  I'm wondering if a call to
csound->Reset() is necessary before deleting the object and if
finalization calls to stop threads isn't happening for some reason.

steven

On Mon, Mar 1, 2010 at 1:39 PM, Victor Lazzarini
 wrote:
> (gdb) backtrace
> #0  0x000953a2 in ?? ()
> #1  0x00086f2f in ?? ()
> #2  0x00079477 in ?? ()
> #3  0x0007d07d in ?? ()
> #4  0x000879ee in ?? ()
> #5  0x97013155 in _pthread_start ()
> #6  0x97013012 in thread_start ()
>
> This is from a crash using a simple CSD with -d  -otest.wav  -M0 and
> portmidi, with the following program:
>
> #include 
> #include 
> #include 
> #include 
>
> int main(int argc, char **argv){
>
>   Csound *cs;
>
>   for (int i =0; i < 5; i++) {
>     fprintf(stdout, "=========== PLAY TIME %d ===========\n", i+1);
>   cs = new Csound();
>   cs->Compile(argc, argv);
>   cs->Perform();
>   delete cs;
>   }
>   return 0;
> }
>
> Why is pthread_start() being called? This should be single-thread.
> What's this thread being started and crashing? Can anyone explain? Is
> that outside Csound?
>
> Victor
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Steven,

no, that does not make a difference. It's this CFMessagePort error  
message I am getting, which wasn't there before, that seems to be  
related to the problem.

Victor
On 1 Mar 2010, at 22:37, Steven Yi wrote:

> Hi Victor,
>
> Just had a thought, does this fail before compilation, during
> performance, or after performance?  I'm wondering if a call to
> csound->Reset() is necessary before deleting the object and if
> finalization calls to stop threads isn't happening for some reason.
>
> steven
>
> On Mon, Mar 1, 2010 at 1:39 PM, Victor Lazzarini
>  wrote:
>> (gdb) backtrace
>> #0  0x000953a2 in ?? ()
>> #1  0x00086f2f in ?? ()
>> #2  0x00079477 in ?? ()
>> #3  0x0007d07d in ?? ()
>> #4  0x000879ee in ?? ()
>> #5  0x97013155 in _pthread_start ()
>> #6  0x97013012 in thread_start ()
>>
>> This is from a crash using a simple CSD with -d  -otest.wav  -M0 and
>> portmidi, with the following program:
>>
>> #include 
>> #include 
>> #include 
>> #include 
>>
>> int main(int argc, char **argv){
>>
>>   Csound *cs;
>>
>>   for (int i =0; i < 5; i++) {
>>     fprintf(stdout, "=========== PLAY TIME %d ===========\n", i+1);
>>   cs = new Csound();
>>   cs->Compile(argc, argv);
>>   cs->Perform();
>>   delete cs;
>>   }
>>   return 0;
>> }
>>
>> Why is pthread_start() being called? This should be single-thread.
>> What's this thread being started and crashing? Can anyone explain? Is
>> that outside Csound?
>>
>> Victor
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net