[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

896.0. "More on watch points" by CXXC::REINIG (This too shall change) Fri Mar 21 1997 16:02

I tried to use watch in Ladebug Debugger Version 4.0-33.  It caught the
first change to the watched thing (actually, it caught a change in the
thing next to what I'm interested in).

    (ladebug) watch (&sym->fe_specific)
    [#2: watch 0x14090958 to 0x1409095f ]

    (ladebug) cont
    [2] The contents at address range 0x14090958 to 0x1409095f
        was accessed by instruction 0x2443bf58
            Old value = 335926240
            New value = 2547053381407712
    [2] stopped at [gem_st_insert_symbol_node:3358 0x2443bf5c]
    (Cannot find source file GEMSRC/gem_st.bli)

    (ladebug) 0x14090958 / X
    0x14090958: 14090c881405d3e0

Continuation after the watch resulted in the debugger spinning

    (ladebug) cont
    ... nothting happens as ladebug chews up CPU resources

Bevin explained to me what was happening, then he typed in the following
command.  

    (ladebug) ($pc)/10i
    
    Ladebug Debugger Version 4.0-33 caught signal "Segmentation fault" (11).
    This is an unexpected condition and may indicate the presence of a defect.
    If you wish to report this, please include the stack trace that follows.
    Diagnostic stack trace ...
    PC is zero - stack trace not available.
    end of diagnostic stack trace.
    
    Compilation terminated.
    Abort (core dumped)
 
He hemmmed over the result and said yes when I asked if I should post it.

                                    August    
T.RTitleUserPersonal
Name
DateLines
896.1TLE::CHIUFri Mar 21 1997 17:335
Thanks for reporting this problem.  Could I have a pointer to
a reproducer for it?

Caroline
896.2CXXC::REINIGThis too shall changeMon Mar 24 1997 09:1238
Look in /usr/users/reinig/public for exx and abs.cxx

    cxxosf> ladebug /usr/users/reinig/public/exx
    Welcome to the Ladebug Debugger Version 4.0-33
    ------------------
    object file name: /usr/users/reinig/public/exx
    Reading symbolic information ...done
    Directory search path for source files:
     . /usr/users/reinig/public .
    (ladebug) stop in note_sym_tuple
    [#1: stop in void note_sym_tuple(GEM_TUPLE*, GEM_SYMBOL*) ]
    (ladebug) run abs.cxx
    [1] stopped at [note_sym_tuple:1488 0x6ffe45dc]
       1488     efd = efd_of_gem_symbol(sym);
    (ladebug) watch (&sym->fe_specific)
    [#2: watch 0x14090ca0 to 0x14090ca7 ]
    (ladebug) cont
    [1] stopped at [note_sym_tuple:1488 0x6ffe45dc]
       1488     efd = efd_of_gem_symbol(sym);
    (ladebug) delete 1
    (ladebug) cont
    ***press control C sometime after the continue.***
    (ladebug) ($pc)/10i
    
    Ladebug Debugger Version 4.0-33 caught signal "Segmentation fault" (11).
    This is an unexpected condition and may indicate the presence of a defect.
    If you wish to report this, please include the stack trace that follows.
    Diagnostic stack trace ...
    PC is zero - stack trace not available.
    end of diagnostic stack trace.
    
    Compilation terminated.
    Abort (core dumped)
    
In the course of reproducing this I found that I can't always cause the
crash.  

                                        August
896.3TLE::BRETTThu May 29 1997 16:161
All (?) ^C problems are fixed in BL38