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
