Newsgroups: comp.sys.mac.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!ames!ads.com!killer!usenet
From: anders@verity.com (Anders Wallgren)
Subject: Re: Jump Table Offset error..
Reply-To: anders@verity.com (Anders Wallgren)
Organization: Verity, Inc., Mountain View, CA
Date: Mon, 1 Apr 91 01:51:13 GMT
Message-ID: <1991Apr1.015113.9283@verity.com>
In-Reply-To: gb2a+@andrew.cmu.edu (George J. Baxter)
References: <obwsMSa00WBNI1lkkK@andrew.cmu.edu>
Sender: usenet@verity.com (USENET News)

In article <obwsMSa00WBNI1lkkK@andrew.cmu.edu>, gb2a+@andrew (George J. Baxter) writes:
>
>    I have a nagging problem that is occuring with MPW.. I'm linking in
>some external procedures to a larger program, and one group of
>procudures keeps resulting in and error:
>
> ### Link: Error: Jump Table Offset is out of range. (Error 50) HandleMacEvents
>


The problem is that MPW doesn't allow you to jump to a function in
another segment if that function is more than 32K into the segment.
This limitation arises because the jump table that is constructed to
allow inter-segment jumping uses a 16-bit offset into code segments.
This limitation will be removed when MPW 3.2 is released.

The answer (unfortunately for you since you didn't write the code) is
to make sure that the segment that your external procedure is in gets
split up into smaller segments.


anders