Are you writing web publishing code that runs on the server? Or are you saying that you are working with a shared database and code you are running on the client is causing the server to crash?
I think you probably mean the latter though that would leave me a bit stumped. When working with a shared database, no code you write ever runs on the server, your code only runs on the client. There are about two dozen simple commands that the client can communicate to the server – open database, close database, synchronize, lock record, unlock record, add record, delete record, etc.
You say that it crashes every time you run “the code”, so that should make it easier to track down. So first of all, please verify that this code is running on the client. Second, what does this code do? Is it simple or something long and complex? If the code is on the client, what does it do when the server crashes? I would assume it would hang waiting for the server to reply? In that case I would add instrumentation to your client code and run it to see how far it gets.
Are you starting the server via Terminal, the client via Terminal, or both?
Like Thomas, I am puzzled by this. Maybe you meant when viewed from the Panorama X Preferences:Server panel? When Panorama X Server is running, it “advertises” its presence on the network via Bonjour. The preference panel checks for this to show whether the server is running or not. If the server quits for any reason (including crashing), it will automatically stop broadcasting it’s presence via Bonjour. So if it does crash, it will indeed show that it is “Stopped” in the preference panel. However, that isn’t really useful diagnostic information.