[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

308.0. "MAPS for server" by OIWS20::BRYSON () Sun Feb 26 1989 23:56

    Are the maps for the DECW$SERVER_DIX.EXE and DECW$SERVER_DDX*.EXE
    going to be available to internals so that we may either analyze
    a server crash or analyze a running server?  The DDX maps are
    most important since we will have to trace problems by had through
    this code.
    
    David
T.RTitleUserPersonal
Name		DateLines
308.1MAPS are there, how about machine code?CSC32::M_POTEETWed Apr 05 1989 17:4327
    The RESD that we received here in Colorado has SERVER maps (among
    others):
    
    RESD:[SERVER.V51.SERVER.LIS]DECW$SERVER_MAIN.MAP
    RESD:[SERVER.V51.SERVER.LIS]DECW$SERVER_DIX.MAP
    RESD:[SERVER.V51.DDXGPX.LIS]DECW$SERVER_DDX_GA.MAP
    RESD:[SERVER.V51.DDXLEGSS.LIS]DECW$SERVER_DDX_GB.MAP
    RESD:[SERVER.V51.DDXMFG.LIS]DECW$SERVER_DDX_GC.MAP  
    RESD:[COMMON.V51.TRANSPORT.LIS]DECW$TRANSPORT_*.MAP
    
    The one issue that I have with the RESD is that the *.LIS files
    produced from the C compilations are (practically) useless since
    they do not contain machine-code listings.  Trying to find the code
    for a particular PC within a C module becomes very troublesome...I
    end up starting from some "known" offset (e.g. useful CALLS or
    beginning of routine) and tracing macro code to the correct PC (yuck!).
    
    If we can get feedback to whoever generates the RESD's in the first
    place, PLEASE put a /MACHINE on the compilation.
    
    Any hints from developers who have probably done PC -> codefrag
    translation w/o machine code listings would be appreciated.
    
    mTp