RUNREV Technical support
bdrunrev at gmail.com
Fri Jan 23 15:15:45 CST 2009
Perhaps this is another instance where a debug-logging engine would produce
information that would lead to a speedier identification of the problem?
On Fri, Jan 23, 2009 at 7:36 PM, J. Landman Gay <jacque at hyperactivesw.com>wrote:
> Dave wrote:
> So, why doesn't RunRev provide a version of the Standalone builder that
>> dumps a trace to a log file?
> I asked one of the engineers about this today. There is no SB prepared that
> includes logging at present. But the consensus was that it wouldn't help
> anyway. The Standalone Builder is just a stack like any other, and since it
> seems the script is aborting for some reason, any scripted logging would
> abort too. That would tell us where the process left off, of course, but we
> already know where that happens, given the file that is left in RAM. I asked
> the engineer to rebuild the sample stack yet again today and it still builds
> fine for him, as it has for everyone else who's tried it.
> At any rate, he has offered to look at Steve's actual production stack. I
> will be sending instructions privately on how to get the file to RR if Steve
> is willing. They will try it at no charge to him.
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
More information about the use-livecode