Run csound in the debugger (i.e. gdb) and when it crashes, you may be able to type 'bt' in the debugger and see a stack trace. Then you can copy it and send it to us.

-----Original Message-----
From: Iain Duncan 
Sent: Apr 5, 2005 3:29 PM
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] csound5 request, urgent

Sure. I think. What's a backtrace? ; )

Iain


Istvan Varga wrote:
> Iain Duncan wrote:
> 
>> sread requesting more memory
>> Csound Tidyup Segmentation fault.
> 
> 
> Could you post a backtrace ?
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Tue, 5 Apr 2005 17:56:32 -0400 (GMT-04:00), Michael Gogins  
 wrote:

> Run csound in the debugger (i.e. gdb) and when it crashes, you may be  
> able to type 'bt' in the debugger and see a stack trace. Then you can  
> copy it and send it to us.


Or alternatively,  in the shell,type " ulimit -c unlimited" before you run  
csound.
Then when it crashes you get a core dump called core.[pid_number]
Then do gdb csound core.[pid_number] and type bt on the gdb prompt.

Where [pid_number] is the process id number of the csound process that  
just crashed.

That might work better if you are running rt audio, because running inside  
a debugger will slow things down a lot.

Gerard



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net