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

Conference turris::decladebug

Title:Digital Ladebug debugger
Moderator:TLE::LUCIA
Created:Fri Feb 28 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:969
Total number of notes:3959

293.0. "DECladebug Version 4.0-9 Where command causes DecLadebug to crash" by TLE::KIMBALL (Keith Kimball 381-0573) Thu Aug 24 1995 14:03

T.RTitleUserPersonal
Name
DateLines
293.1UHUH::SHAMIMMon Aug 28 1995 11:355
293.2support for OPTIONAL parameters neededUHUH::SHAMIMTue Aug 29 1995 10:5225
293.3Thanks for the information and workaroundTLE::KIMBALLKeith Kimball 381-0573Tue Aug 29 1995 12:277
293.4closedTLE::LUCIAhttp://asaab.zko.dec.com/~lucia/biography.htmlMon Apr 28 1997 17:4218
    (ladebug) t
    >0  0x12000181c in mysub(FIRST=0, SECOND=0, THIRD=0, FOURTH=<no value>,
    FIFTH=<no value>) l293.f90:8
    #1  0x1200018c4 in optarg() l293.f90:38
    #2  0x1200017cc in main() for_main.c:203
    (ladebug) c
    [1] stopped at [mysub:8 0x12000181c]
          8       end subroutine mysub
    
    
    Well, we don't core dump, but we don't do anything special for the
    un-passed parameters.  <no value> is the default behavior for
    referencing parameter passed by reference whose address is zero.  This
    is the defined behavior from Fortran's persepective.  There is still
    nothing in the symbol table which indicates that any parameters may be
    optional.  We need this part to alloc CALLing a routine with optional
    parameters from the command line (on the to-do list already)