More information. On a different machine, *ubuntu 1, apache2, livecode-server 4-6-3* there is also a signal 11, but quite a bit more info (that I don't understand.)
livecode-server exited due to fatal signal 11 in __kernel_sigreturn @ 0 in <unknown> @ 0x8158f85 in <unknown> @ 0x809e596 in <unknown> @ 0x809ea13 in <unknown> @ 0x809eccc in <unknown> @ 0x809177d in <unknown> @ 0x8091fed in <unknown> @ 0x81cd09e in <unknown> @ 0x81c96d3 in <unknown> @ 0x81c9b40 in __libc_start_main @ 231 in fwrite @ 305 I'm going to re-download the livecode server distributions on the off chance theres been a sneaky fix or update that I haven't seen, but at this point i'm without clue. Which is of course my usual state of being! *grin* Will send a note to support in a day or so if nobody can point me to whatever mistake I made. Thanks in advance for any help On Wed, Jul 27, 2011 at 8:34 AM, Mike Bonner <bonnm...@gmail.com> wrote: > Has anyone managed to get a stack to load using livecode-server for > windows? All I get is "livecode-server exited due to fatal signal 11" > > This happens when trying to library the stack as well as using go stack > <stackpath> > > Otherwise livecode-server is working great, just can't get the stack > support to work. > > I've even checked it from the command line to make sure that I don't have > some strange apache misconfiguration going on, but the result is the same. > > > Any suggestions? > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
