Article View: comp.sys.mac.oop.macapp3
Article #324RE: Segment woes
From: RON_REUTER
Date: Thu, 21 Jan 1993 18:04
Date: Thu, 21 Jan 1993 18:04
78 lines
3723 bytes
3723 bytes
Boy, do we need a FAQ or what? This question pops up every 2 months or so. Here're some answers from a previous link that may help: Item 6391060 4-Sept-92 18:30PDT From: KSAND Sandvik, Kent ------------------------------------------------------------------------------ Sub: RELinker Errors, HELP!!! ----Linking: HTool ### LPS 105:Latest MPW:MPW:Tools:Link: Error: Jump table offset into code segment is greater than 32K. (Error 50) TFILESCOMMAND_INITIALIZEFROMAPPLEEVENT ### LPS 105:Latest MPW:MPW:Tools:Link: Error: Jump table offset into code segment is greater than 32K. (Error 50) TFILESCOMMAND_INITIALIZE ### LPS 105:Latest MPW:MPW:Tools:Link: Error: Jump table offset into code segment is greater than 32K. (Error 50) TODOCCOMMAND_IODOCCOMMAND I've tried resegmentation without any improvement. These objects would seem to be in the MacApp code itself and not my code. ----- Ouch, I've given sort of consulting answers to this question so many times. It will be part of a new TN that we are hopefully shipping in a month's time (Illuminations on MacApp Segmentation, imagine a bunch of monks working on a very expensive book :-) ). Anyway, the error messages says it all. Trick to go around the 16-bit offset problem: a) Try using the link -sortsg flag that will move the most called functions within 16-bit offsets inside the segment. May work, may not. b) Use model far, no more pc-relative problems (32-bit offsets). c) Move Runtime.o as near the Main .o file as possible (hack in either the Makeit produced file, or move things around in the "Build Rules and Dependencies" so Runtime.o is nearer the self produced .o files. d) Segment things so that calls are done inside the same segment (no jump tables needed). There might be other clever clues. ________________________________________________________ From: PETER_BOSANKO@qmrelay.mail.cornell.edu on Thu, Jan 21, 1993 2:27 PM Subject: Segment woes To: MacApp 3 Technical Discussion This message was sent using a custom form that is not installed on your server. Some information from the original message may not be displayed. To view the complete message, ask your network manager to install the form on your server. AppleLink gatewayed addresses are limited to 35 characters, and this letter has a longer return address. It has been mapped into the address above. Reply using that address, and everything should work. The actual address is in the Internet headers below. From: "Peter Bosanko" <Peter_Bosanko@qmrelay.mail.cornell.edu> To: "MacApp3 Tech$" <MacApp3Tech$@applelink.apple.com> GatorMail-Q Segment woes Hello, I'm experiencing a strange error... ### Goliath:MPW:Tools:Link: Error: Jump table offset into code segment is greater than 32K. (Error 50) .READFROM ... when my MacApp 3.0.1 program is being linked. It happened after I added a couple of new classes to my App. I thought at first that it might be because one of my segments had gotten too big. So I made sure all the new code was in a segment on its own. It still gets this error. Has anyone seen this before? Does this mean that I don't have space in my Jump Table? Any insights would be appreciated. Pete Bosanko Cornell Information Technologies
Technical Details
Message-ID:
<9301222112.AA03942@uswmrg.mrg.uswest.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!olivea!apple!applelink.apple.comShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!apple!applelink.apple.com From: RON_REUTER@MSMGATE.MRG.USWEST.COM Newsgroups: comp.sys.mac.oop.macapp3 Subject: RE: Segment woes Message-ID: <9301222112.AA03942@uswmrg.mrg.uswest.com> Date: 21 Jan 93 18:04:00 GMT Sender: daemon@Apple.COM Organization: AppleLink Gateway Lines: 78