Re: [sc-dev] scsynth crashes

[James Harkins <jamshark70@xxxxxxxxx>]

You can disregard the crash dump I sent earlier... just noticed it was from a couple of weeks ago.

The console log has the following entry, but no crash dump was written to scsynth.crash.log. But, the server went down. No /quit message would have been sent in my process.

Weird.

James

Dec  7 15:53:28 Isabelle crashdump: getpwuid("7340140") failed

Dec  7 15:53:28 Isabelle crashdump: getpwuid("7340140") failed

Dec  7 15:53:28 Isabelle crashdump: Crash report written to: /Library/Logs/CrashReporter/scsynth.crash.log

Dec  7 15:53:28 Isabelle crashdump: getpwuid("1936880177") failed

Dec  7 15:53:29 Isabelle /usr/libexec/crashreporterd: exception_raise() failed forwarding exception: (os/kern) invalid argument

Dec  7 15:53:29 Isabelle /usr/libexec/crashreporterd: newport: 2a03 originalport: b07 thread: b403 task: b503 exception: 1

Dec  7 15:53:29 Isabelle /usr/libexec/crashreporterd: mach_msg() reply failed: (ipc/send) invalid destination port

->TempoClock_stopAll 00000000
<-TempoClock_stopAll 00000000
err 0
rm: synthdefs/temp__*: No such file or directory

On Sunday, Dec 7, 2003, at 15:55 US/Eastern, James Harkins wrote:

> I've had a couple of scsynth crashes while working on my adaptive sequencing routines. It occurs after I've been running the routine for a few minutes. The routine runs normally then stops abruptly with NodeWatcher complaining about a null nodeID. At that time I notice the synth has crashed. There is no RESULT = in the output window.
>
> I'm using the default synthdef, nothing fancy.
>
> I haven't done a cvs update in a while so I'll rebuild now and try again after that.
>
> Any ideas?
>
> James
____________________________________

H. James Harkins /// dewdrop_world
http://www.duke.edu/~jharkins

"If attacked by a lion, thrust your arm down his throat.
This takes some practice."  -- Cyril Connolly