Rev IDE crashing

[Chris Sheffield]

I'm not even specifying modes.  It simply reads 'go stack "RNStories"'.

What I've got is a custom handler 'GoStories' that is called from a mouseUp
handler of a button.  It looks like this:

   on GoStories
      lock screen
      go stack "RNStories"
      set the visible of stack "RNLogin" to false
      unlock screen
   end GoStories

Is there anything unusual there?  The thing that's really strange is that
this same code has been working for months now with different versions of
Rev on OS X, and it still works fine under Windows with Rev 2.1.  It wasn't
until I moved the stack to OS X and Rev 2.1 that I've had this problem.

I'm going to keep playing with it a bit.  I logged the crash like Alex said,
and it appears that my code is trying to access some area of memory that it
shouldn't.  I could be wrong about that, though.  I'm not familiar with Mac
programming other than in Rev, but I've seen similar messages in a C
debugger on Windows.  If I can't figure anything out I'll go ahead and bug
report it.  Thanks to you and Alex.

Chris Sheffield
Software Development
Read Naturally
csheffield at readnaturally.com


-----Original Message-----
From: use-revolution-admin at lists.runrev.com
[mailto:use-revolution-admin at lists.runrev.com] On Behalf Of Jan Schenkel
Sent: Monday, September 08, 2003 11:31 AM
To: use-revolution at lists.runrev.com
Subject: Re: Rev IDE crashing

--- Chris Sheffield <revlist at cableone.net> wrote:
> If the Rev IDE crashes, is there any way to find out
> why?  Like a log file
> or something that is written to?
> 
> I'm working on OS X 10.2.6.  I've got a main stack
> that opens another stack
> via the go command.  I've debugged it and Rev
> crashes every time on the line
> with the go command.  I cannot figure out what's
> going on, and I can't debug
> any further because it crashes.  I'm not sure if
> I've got bad code in the
> handlers of the new stack or not.  But the exact
> same thing runs fine under
> Windows.  I've tried placing breakpoints in my
> preOpenStack and preOpenCard
> handlers to no avail.  It seems like the go command
> is actually what's
> failing.
> 
> Can anyone think of anything else I could check for
> or do?
> 
> Thanks,
> 
> Chris Sheffield
> 

Hi Chris,

Alex gave you instructions on how to log the crash.
In the meantime, what is the exact 'go' statement ?

There is/was a bug that could cause a crash with :
  go stack "Foobar" in window of this stack
if the stacks have different stack modes (topLevel,
modal,...)

If that's the case, then try changing the modes to
match first.

Hope this helped,

Jan Schenkel.

=====
"As we grow older, we grow both wiser and more foolish at the same time."
(La Rochefoucauld)

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
_______________________________________________
use-revolution mailing list
use-revolution at lists.runrev.com
http://lists.runrev.com/mailman/listinfo/use-revolution