Subject: | |
From: | |
Reply To: | |
Date: | Fri, 9 Feb 2001 10:20:32 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
All,
I was checking out some of our user XLs (libraries we provide with our
product) and was horrified (well, not that extreme) to find that there were
system entry points listed in our user modules. Examples are Image calls,
NetIPC calls, and calls like FOPEN, IOWAIT.....
Now, I noticed that LINKEDIT shows these as "stubs external" so maybe we are
not really loading system routines into our user libraries (whew).
So, am I safe to assume that these system entry points shown as "stubs
external" are merely references to those entry points in the system
libraries, included merely for the benefit of the user routines (in the
module) that call them?
What's the technical skinny on this? Perhaps I should RTFM?
-Dave
Here's and example:
MODULE NAME : SL010781
TEXT SIZE : 000006A8
DATA SIZE : 00000000
VERSION : 87102412
LENGTH : 00002714
SHARED DATA : NO
Sym C H X P Sym Sym Sym Lset
Name Type Scope Value Name
---- - - - - ---- ----- ----- ----
drdbdelete 0 3 3 entry univ 0000E378
drdblock 0 3 3 entry univ 0000E3EC
drdbopen 0 3 3 entry univ 0000E460
drdbput 0 3 3 entry univ 0000E4D4
drdbupdate 0 3 3 entry univ 0000E55C
sl010 0 3 3 entry univ 0000E070
$RECOVER_END 0 code univ 0000E6A8
$RECOVER_START 0 code univ 0000E6A8
$UNWIND_END 0 code univ 0000E648
$UNWIND_START 0 code univ 0000E5E8
drdbdelete 0 code univ 0000E3B4
drdblock 0 code univ 0000E428
drdbopen 0 code univ 0000E49C
drdbput 0 code univ 0000E510
drdbupdate 0 code univ 0000E598
sl010 0 code univ 0000E10C
P_CLOSE_FILES 0 stub ext lp+00000120
P_REWRITE 0 stub ext lp+000000E0
P_WRITELN 0 stub ext lp+00000020
P_WRITESTR 0 stub ext lp+000000C0
dbdelete 3 stub ext lp+00000100
dblock 3 stub ext lp+00000040
dbopen 3 stub ext lp+00000060
dbput 3 stub ext lp+00000080
dbupdate 3 stub ext lp+000000A0
|
|
|