[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

390.0. "Browse Source... is it broken?" by GOLLY::BRODEUR (Michael Brodeur) Tue Jan 09 1996 13:00

T.RTitleUserPersonal
Name
DateLines
390.1Need a test pgm which reproduces the problemUHUH::MAHONEYThu Jan 11 1996 09:515
390.2Reproducing the problem - NOT!GOLLY::BRODEURMichael BrodeurTue Jan 16 1996 10:0121
390.3Status?TLE::LUCIAhttp://asaab.zko.dec.com/~lucia/biography.htmlFri May 02 1997 10:226
    The behavior as described still exists, that is, double clicking on a
    function name sets a breakpoint.  Single clicking highlights the
    function, but doesn't offer much of a choice beyond that.
    
    What is the desired and/or intended behavior?
    
390.4Haven't used it in a whileTLE::BRODEURMichael BrodeurMon May 05 1997 10:4018
I will admit that I haven't used dxladebug in quite some time, so the issue
is a little foggy for me, but as I recall ---

If you open the Browse Source window and start double clicking on items in
the list, the view expands to show you successively more detail about what
you are clicking on.  That is, if you double click on an EXE you see the
libraries, doub
le click on the libraries and you get the file, double click on
the file and you get a list of functions.

What I expected to happen was for this behavior to continue, that is, double
click on the function and it shows you the function (in the source window).
If I remember correctly, what it does instead is (in my opinion) to totally
change its behavior by not showing me more information, but taking an
action (setting a breakpoint).  I (personally) would prefer that it showed
you the function in the source display instead.

--Mike