Crash on Standalone build - Help please
ron barber
rbarber at yhb.att.ne.jp
Mon Aug 2 23:53:30 EDT 2004
Ah...I think this is one I've recently found too!
I changed the main stack to visible and that solved the problem, viz. I
can successfully build the standalone. I find it hard to believe no one
else has run into this, since I thought it was a fairly standard
procedure. At any rate, thanks for the prompt support and solution.
I'll keep it visible until it can be built the way it should be.
So this is a problem for 2.2 and for 2.2.1 and the only fix is to get
2.5?
Thanks for you work,
Ron
On Aug 3, 2004, at 12:37 PM, Monte Goulding wrote:
> Ah.. I think this is one I've recently found and fixed. A temporary
> workaround would be to set the visible of the mainstack to true. The
> fix
> will be in Beta 2 of 2.5.
>
> Cheers
>
> --
> Monte Goulding - monte at sweattechnologies.com
> Sweat Technologies
>
> InstallGadget - How To Create An Installer In 10 Seconds
> http://www.sweattechnologies.com/InstallGadget
>
>
>> -----Original Message-----
>> From: use-revolution-bounces at lists.runrev.com
>> [mailto:use-revolution-bounces at lists.runrev.com]On Behalf Of ron
>> barber
>> Sent: Tuesday, 3 August 2004 12:59 PM
>> To: How to use Revolution
>> Subject: Re: Crash on Standalone build - Help please
>>
>>
>> Hi Monte
>>
>> thanks for the reply. The application has an invisible main stack
>> palette and a visible sub-stack palette along with other substacks
>> that
>> open as needed.
>>
>> It crashes during the standalone build. It ask if I want to save
>> changes. Yes or no, the result is the same. In the 'yes' case, it
>> saves
>> changes, closes the window. Then the mainstack flashes open and
>> closes,
>> the visible substack opens and shortly thereafter, RR crashes.
>>
>> What else would be helpful to know?
>> Ron
>>
>> On Aug 3, 2004, at 12:02 PM, Monte Goulding wrote:
>>
>>>
>>> Can you give some more details. Is it crashing during the standalone
>>> build
>>> process or when you try to launch your standalone?
>>>
>>> Cheers
>>>
>>> --
>>> Monte Goulding - monte at sweattechnologies.com
>>> Sweat Technologies
>>>
>>> InstallGadget - How To Create An Installer In 10 Seconds
>>> http://www.sweattechnologies.com/InstallGadget
>>>
>>>
>>>> -----Original Message-----
>>>> From: use-revolution-bounces at lists.runrev.com
>>>> [mailto:use-revolution-bounces at lists.runrev.com]On Behalf Of ron
>>>> barber
>>>> Sent: Tuesday, 3 August 2004 12:17 PM
>>>> To: How to use Revolution
>>>> Subject: Crash on Standalone build - Help please
>>>>
>>>>
>>>> Greetings
>>>>
>>>> Can someone tell me what this crash log is telling me? I am trying
>>>> to
>>>> build a standalone which in the past has built successfully. RR can
>>>> build several other stacks into standalones successfully, but this
>>>> stack crashes every time. Any help would be greatly appreciated.
>>>>
>>>> thanks
>>>> Ron
>>>> ==================
>>>>
>>>> Date/Time: 2004-08-03 11:28:57 +0900
>>>> OS Version: 10.3.4 (Build 7H63)
>>>> Report Version: 2
>>>>
>>>> Command: Revolution
>>>> Path: /Users/reb/Documents/MacSeisho dev/current build/Revolution
>>>> 2.2.1/Revolution.app/Contents/MacOS/Revolution
>>>> Version: 2.2.1 (2.2.1)
>>>> PID: 742
>>>> Thread: 0
>>>>
>>>> Exception: EXC_BAD_ACCESS (0x0001)
>>>> Codes: KERN_INVALID_ADDRESS (0x0001) at 0x066570c8
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> use-revolution mailing list
>>>> use-revolution at lists.runrev.com
>>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>>
>>>
>>> _______________________________________________
>>> use-revolution mailing list
>>> use-revolution at lists.runrev.com
>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>
>>
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
More information about the use-livecode
mailing list