🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.next.programmer
2 messages
2 total messages Started by Robert D. Nicholson Sat, 21 Nov 1992 09:07
rld: undefined symbols
#1869
Author: Robert D. Nicholson
Date: Sat, 21 Nov 1992 09:07
11 lines
664 bytes
I am writing a Workspace contents inspector.

Upon trying to load the bundle I get the following
message on the console.

/robert/Apps/RIBInspector.bundle/RIBInspector

Nov 21 19:59:45 steffi WM[148]: rld(): Undefined symbols:

My Bundle's nib has a customView is this legal with bundles?
Re: rld: undefined symbols
#1896
Author: Bill Bumgarner
Date: Mon, 23 Nov 1992 16:35
74 lines
2934 bytes
In article <1992Nov21.090743.8818@monu6.cc.monash.edu.au>  
ede978e@monu6.cc.monash.edu.au (Robert D. Nicholson) writes:
> 
> I am writing a Workspace contents inspector.
> 
> Upon trying to load the bundle I get the following
> message on the console.
> 
> /robert/Apps/RIBInspector.bundle/RIBInspector
> 
> Nov 21 19:59:45 steffi WM[148]: rld(): Undefined symbols:
> 
> My Bundle's nib has a customView is this legal with bundles?
> 

Assuming that by saying customView, you mean that you have a custom subclass of  
the view class-- in this case, probably a subclass of N3DMovieCamera-- yes,  
this is allowable within a bundle.  The source files (whatever.[hm]) should  
just be added to the bundle project like any other source files.

That rld() message is totally useless-- and not uncommon.  There is an annoying  
bug in rld such that it doesn't dump a complete message to console.  It DOES  
work under gdb-- so you might try attaching gdb to the WM process:

gdb /usr/lib/NextStep/Workspace.app/WM.app/WM
attach 148

<< go inspect a .rib file here and it should give you a useful message >>

In the best case, there is simply some function/class being referenced that you  
have forgotten to include in your code or have mis-typed it (any compiler  
warnings when you compile the code?).

In the worst case, the undefined symbol is N3DCamera itself because WM.app  
doesn't include libMedia-- looking at WM.app/WM via otool -l, one gets:

Load command 6
           cmd LC_LOADFVMLIB
       cmdsize 56
          name /usr/shlib/libIndexing_s.A.shlib (offset 20)
 minor version 1
   header addr 0x0a000000
Load command 7
           cmd LC_LOADFVMLIB
       cmdsize 52
          name /usr/shlib/libNeXT_s.C.shlib (offset 20)
 minor version 57
   header addr 0x06000000
Load command 8
           cmd LC_LOADFVMLIB
       cmdsize 48
          name /usr/shlib/libsys_s.B.shlib (offset 20)
 minor version 55
   header addr 0x05000000
Load command 9
     cmd LC_SYMTAB
 cmdsize 24
  symoff 524288
   nsyms 5106
  stroff 585560
 strsize 121640


Which seems to indicate that WM.app doesn't have any kind of a reference to  
libMedia_... which would leave the 3Dkit (and anything else in that lib-- live  
video, as well) inaccessible...

One COULD potentially edit the load commands....

--
Bill Bumgarner <bbum@object.com> | "The devils of truth...
Objective Technologies, Inc.     |    steal the souls of the free." -- NIN
-- 
Bill Bumgarner <bbum@object.com> | "The devils of truth...
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads