Segmentation fault (core dumped) RESULT = 35584

View: New views
4 Messages — Rating Filter:   Alert me  

Segmentation fault (core dumped) RESULT = 35584

by Martin . :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I'm trying to understand

Segmentation fault (core dumped)
RESULT = 35584

which quits the server.

This happens in a setup where a lot of synths are created. As far as
I've tried to trace the reason, I've got 23 synths and 500 ugens
running.

Are there any directions I should focus on to trace the problem that
anyone knows of?

Cheers,
Martin
_______________________________________________
sc-users mailing list
sc-users@...
http://lists.create.ucsb.edu/mailman/listinfo/sc-users

Re: Segmentation fault (core dumped) RESULT = 35584

by Josh Parmenter :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

SOmething that is using (or wants to be using) a memory buffer is  
having a problem. Look for UGens that need memory, and see if you may  
be passing in a bad buffer number.

Best,

Josh

On May 15, 2008, at 4:36 PM, Martin . wrote:

> Hi,
>
> I'm trying to understand
>
> Segmentation fault (core dumped)
> RESULT = 35584
>
> which quits the server.
>
> This happens in a setup where a lot of synths are created. As far as
> I've tried to trace the reason, I've got 23 synths and 500 ugens
> running.
>
> Are there any directions I should focus on to trace the problem that
> anyone knows of?
>
> Cheers,
> Martin
> _______________________________________________
> sc-users mailing list
> sc-users@...
> http://lists.create.ucsb.edu/mailman/listinfo/sc-users

******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own  
interpretation of how modern society is structured: whether actively  
or passively, consciously or unconsciously, he makes choices in this  
regard. He may be conservative or he may subject himself to continual  
renewal; or he may strive for a revolutionary, historical or social  
palingenesis." - Luigi Nono
*/

_______________________________________________
sc-users mailing list
sc-users@...
http://lists.create.ucsb.edu/mailman/listinfo/sc-users

Re: Segmentation fault (core dumped) RESULT = 35584

by stefan kersten-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 16.05.2008, at 01:36, Martin . wrote:
> I'm trying to understand
>
> Segmentation fault (core dumped)
> RESULT = 35584
>
> which quits the server.

this means scsynth tried to access memory that it doesn't own.

> This happens in a setup where a lot of synths are created. As far as
> I've tried to trace the reason, I've got 23 synths and 500 ugens
> running.
>
> Are there any directions I should focus on to trace the problem that
> anyone knows of?

a stack trace would be useful in determining where scynth crashes.
depending on which platform you are on you must recompile scsynth with
the "Development" (as opposed to "Deployment") xcode build variant  
(on osx)
or recompile with scons DEBUG=1 (on linux, not sure about windows).  
start
scsynth inside gdb (the gnu debugger) from the terminal like this:

$ gdb /path/to/scsynth
(gdb) run -u 57110

then, when it crashes

(gdb) backtrace

and post the output.

<sk>

_______________________________________________
sc-users mailing list
sc-users@...
http://lists.create.ucsb.edu/mailman/listinfo/sc-users

Re: Segmentation fault (core dumped) RESULT = 35584

by Martin . :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks Josh, Stefan. I'll check this out.

On Fri, May 16, 2008 at 2:01 AM, stefan kersten <sk@...> wrote:

> On 16.05.2008, at 01:36, Martin . wrote:
>> I'm trying to understand
>>
>> Segmentation fault (core dumped)
>> RESULT = 35584
>>
>> which quits the server.
>
> this means scsynth tried to access memory that it doesn't own.
>
>> This happens in a setup where a lot of synths are created. As far as
>> I've tried to trace the reason, I've got 23 synths and 500 ugens
>> running.
>>
>> Are there any directions I should focus on to trace the problem that
>> anyone knows of?
>
> a stack trace would be useful in determining where scynth crashes.
> depending on which platform you are on you must recompile scsynth with
> the "Development" (as opposed to "Deployment") xcode build variant
> (on osx)
> or recompile with scons DEBUG=1 (on linux, not sure about windows).
> start
> scsynth inside gdb (the gnu debugger) from the terminal like this:
>
> $ gdb /path/to/scsynth
> (gdb) run -u 57110
>
> then, when it crashes
>
> (gdb) backtrace
>
> and post the output.
>
> <sk>
>
> _______________________________________________
> sc-users mailing list
> sc-users@...
> http://lists.create.ucsb.edu/mailman/listinfo/sc-users
>
_______________________________________________
sc-users mailing list
sc-users@...
http://lists.create.ucsb.edu/mailman/listinfo/sc-users