[Prev][Next][Index][Thread]

Re: executor as a Mac developer target



>>>>> "Scott" == Scott Vorthmann <vorth@cmu.edu> writes:
In article <v02130502adde86056342@[128.2.207.202]> Scott Vorthmann <vorth@cmu.edu> writes:


    Scott> Forgive me if this is newbie stuff... I can't get the
    Scott> newsgroup served, and I didn't find an archive of the
    Scott> newsgroup or mailing list.  The FAQ was no help either...

    Scott> I'm a Mac developer, and I'd like to get my app running
    Scott> under Executor.  The app is not working, some versions even
    Scott> crashing the emulator.  I'm wishing I could just do some
    Scott> very simple debugging while running in Executor, to see
    Scott> which unavailable system services I'm relying on.

When Executor hits an unimplemented trap it *should* tell you the trap
name in a dialog, although if it hits a trap before the screen is set
up that might not happen.

If your app runs on a large number of Macs already (especially 68040
based Macs with the cache turned on), then if you can let us have a
copy of the app for testing purposes we can take a quick look and see
what's going wrong.  Since it's already running on a Mac, the problem
is probably on our side anyway.

    Scott> Is there a MacsBug equivalent?  Even a lame, limp one?
    Scott> Something that will break out and show me a stack crawl?

Nothing that we can give the general public.  We have powerful tools
at our disposal over here, though.

    Scott> Any other tips & tricks for Mac developer's like me, who
    Scott> want to "target" Executor?

In general, if you can let us have a copy of your app, that's usually
all that's necessary.

    Scott> Does the "real" Executor come with real documentation?  A
    Scott> developer's kit?  If so, they should be included with the
    Scott> demo... I'd like to avoid shelling out the cash until I
    Scott> know my app can be made to run.

Even in the real version, Executor's documentation is lacking.  We
don't target developers because in general developers need more from
Executor than we can provide (we don't currently implement the trace
bit in the 68040 status word so trick Mac debuggers won't run under
Executor).

    Scott> Thanks,

    Scott> Scott Vorthmann vorth@cmu.edu 1234 Denniston Ave, #2
    Scott> 412/422-8842 Pittsburgh, PA 15217-1329 422-3904 fax

    Scott> http://www.cs.cmu.edu/~vorth/

    Scott> (I'm no longer with CMU... I have a courtesy account.)

If you can't let us have a copy of the app for testing purposes, we
can continue this discussion off the newsgroup and see if we can't
find some way to help you, but by far the easiest and best solution is
to just let us try the app in our debugging environment.

BTW, some of the debugging tools that we use will be briefly mentioned
in our "Executor Internals" paper which I will present about a week
from now at MacHack '96.  After I've presented that paper it will be
available on our web site.  It won't help you, but you might find it
interesting.

--Cliff
ctm@ardi.com


References: