Conference turris::decladebug

886.0. "My take on bug attack order..." by ADA9X::BRETT () Fri Mar 14 1997 10:10

Here is a general categorisation and prioritisation of the bug reports
I have submitted (although other people may well have raised the initial
issues).

I have only been careful about prioritisation of the Fix Immediately
and Fix Soon categories.  It is possible that there are things that are
already fixed in all categories.

/Bevin


Ergonomics

  Fix Immediately
    722.0 Make double-clicking work properly in dxladebug source	
    762.0 dxladebug desperately needs a FIND	   
    790.0 mouse/paste should paste at better place	     
    799.0 MONITOR with no selected = reexecute prev cmd!	

  Fix Soon
    521.0 Show dec and hex values of chars
    524.0 Dont insist on whole path for files
    869.0 watch (address) is great...BUT		
    578.0 Monitor View doesnt come up at the right times
    693.0 BROWSE SOURCE window can't be made thin enough       
    695.0 QUESTION *should* be in front, BROWSE *shouldnt*	 
    707.0 dxladebug needs a RUN and RERUN as well as CONT	 
    716.0 Disabled BPT's left cluttering STATUS	   
    763.0 BRWOSE SOURCE display optimally *worst* layout	

  Fix Later
    520.0 Allow easier referencing of already given      
    537.0 ladebug cant eat its own local-class syntax    
    543.0 CLASS:: not CLASS.
    544.0 static members should be marked static
    546.0 operator int(void);  should not have result type 
    584.0 dxladebug Monitor View dissappears when Local Variables Vie 
    587.0 "Monitor {" doesnt give error msg 
    635.0 Make ^A behave like it does in Unix, not VMS	  
    636.0 Don't arbitrarily reorder the Breakpoint view list	  
    692.0 dxladebug shouldn't move the source window without being  
    711.0 Selection of selected text doesnt             
    712.0 dxladebug needs a WHATIS button		
    715.0 The blinking THREAD Button		
    757.0 "no value" message is of no value... 	   
    791.0 BPT button cause a blank line to get scrolled       
    793.0 BROWSE SOURCE window not in the VIEWS menu  
    800.0 dxladebug windows have the same icon and text	
    801.0 Appended views should pop up 		
    813.0 dxladebug should move _ to next line 		
    833.0 MONITOR window et al need CLOSE option	    
    842.0 the "^" is in the wrong place		

  Fixed?
    518.0 Bad default font
    583.0 dxladebug unacceptably slow source scroll
    694.0 dxladebug puts returned-to source in wrong place	 
    787.0 scroll performance is as abysmal as ever	     
    829.0 White out the selected choice!		    

Usability
  Fix Immediately
    696.0 dxladebug should support full Unix command lines	 
    786.0 GUI can't set breakpoints		     
    811.0 More than one file named 'eg016.hxx' found in the binary  
    841.0 The BROWSE SOURCE view can't set breakpoints in many ca
    841.0 The BREAKPOINT buttons are simply missing in some cases
    884.0 problems with BPT's caused by #include'ing a file
    885.1 Support for 32-bit REF's  

  Fix Soon
    519.0 cmd line editting cant handle long lines
    522.0 How do I input <generated_names> 
    579.0 dxladebug looses stdin ???
    559.0 Why does ladebug tell me the file for funcs but not vars?
    553.0 Cant set breakpoints in func scope static member funcs
    591.0 Always show the class definition in all its gory
    637.0 Ladebug doesnt understand enumerals            
    641.0 Selecting 'xxx' failed!          
    709.0 Failures to understand enumerals in C,C++	     
    718.0 delete 1-6 7 9 15			
    719.0 The debugger detected an error searching for this breakpoi
    721.0 S<opaque> rather than <opaque>		
    780.0 Examining enumerals is a royal pain in the ...	
    855.0 examine_address mode b=8 x=16 ?=32 X=64	  
    868.0 shared libraries aren't seamless enough	  
    870.0 Search for static variables before complaining...	  
    872.0 "eg_b.cxx"`g12 is/isnt visible in current scope	  
 
  Fix Later
    541.0 whereis <WHAT?>
    542.0 Too many decls of OUTER
    545.0 whereis ~C
    547.0 whereis operator int
    558.0 i, i, sir....
    574.0 Another unremovable monitor
    571.0 Cant remove out-of-scope monitor points
    750.0 [if|while] (exp) {statements} is essential basic function 
    764.0 Add a BACK to the SOURCE window		
    827.0 More MONITOR VIEW woes		    
    860.0 whereis foo? its here here here here here here	  

  Fix Eventually
    527.0 You should be able to input the text you output
    534.0 stop ((C *)0x140000280)->x  TAKES FAR TOO LONG 
    535.0 Undoing 534 takes even longer!!!!
    687.0 show whether or not a function member is static      
    717.0 Command window text output is awful	     

  Fixed?
    679.0 typedef struct C { ... } C;                
    704.0 dxladebug can't set breakpoints on some routines	 
    708.0 dxladebug 4.0-26 jammed lock-solid due to loosing cmd line	     
    841.0 RERUN looses the command line


Correctness
  Fix Immediately
    549.0 class C { typedef enum ... }  glitches
    777.0 RUN should accept a normal Unix command line        
    792.0 enums not visible when should be		 
    794.0 C1::zero is not the same as zero or C2::zero        

  Fix Soon
    548.0 Member functions appear at file scope
    550.0 static member functions hoisted to file scope too
    789.0 duplicate definitions  		 
    798.0 dxladebug truncates very long recalled commands without   
    837.0 Forgot to extend during ptr convertion 	  

  Fix Later
    719.0 The debugger detected an error searching for this breakpoi
    861.0 p ";n;"  symbol substitution is not too bright	  
    804.0 The MONITOR view can not monitor structs.	     
    815.0 instruction view is not maintained reliably	  
    830.0 [MONITOR] sp  doesnt show up in the MONITOR VIEW	  
    831.0 Even more MONITOR VIEW woes		  

  Fix Eventually
    536.0 watchpoints, the code pointed to could not have changed the variable
    710.0 unsigned - literal is UNSIGNED, not SIGNED         
    866.0 W shouldn't do this... 		  
    874.0 p e.D.n1			  

  Fixed?
    523.0 p sizeof("123") prints 0



Correctness of Help

  Fix Soon
    843.0 help printf syntax is wrong                

  Fixed?
    569.0 stop "tmp1.cxx"`main  SHOULD WORK!
    570.0 stop "tmp1.cxx":7  SHOULD WORK

Reliability

  Fix Immediately
    585.0 ladebug can, dxladebug cant find source	     
    586.0 dxladebug cant set bpts  on some fncs	     
    634.0 GUI has breakpoint hassles		      
    758.0 enumType() == e_class src/libsrc/ladebug/type.C 634    
    781.0 ladebug can't coerce simple pointers            
    803.0 getStackInfo: Illegal item code = 28            
    805.0 Value::set(BitsOwn : size == 8)              
    844.0 4.0-29 caught signal "Segmentation fault"	 
    851.0 dxladebug Segmentation fault when CTRL-CLICK	 

  Fix Soon
    605.0 command line of 200 characters hangs dxladebug	
    699.0 First say scope exists, then refuse to find it	
    828.0 error when searching for info on a monitor item.	 

  Fix Later
    552.0 record file is corrupted by err msgs
    554.0 seting bpts on mbr funcs of uninited classes
    573.0 Unimplemented: Type::coerceBits(BitsOwn).
    580.0 More Monitor problems
    602.0 Cant undo typecast in dxladebug monitor	    
    642.0 Internal Error: 4.0-23		      
    748.0 4.0-26 Improperly nested functions should not crash    
    857.0 BACKWARD-QUESTION-MARK in output		 
    863.0 Internal Error: Method not finished yet: ExprNoop::ExprNoo

  Fix Eventually
    582.0 Aborting dxladebug call stack leaves it wrong
       
  Fixed?
    525.0 e main  =>  Compilation terminated./Segmentation fault
    526.0 FILE *doesnt* !!!
    540.0 More problems with watchpoints, now ladebug segment violates!
    588.0 BREAKPOINT VIEW box doesnt show all bpts	     
    680.0 ladebug looses pointer size  	      
    703.0 Ladebug Debugger Version 4.0-26 caught signal "Illegal in 
    706.0 Assertion failed: enumType() == e_class src/libsrc/ladebu 
    720.0 debugger detected an error in the size of the command buf 
    788.0 ots_location_alpha.s still kills ladebug          
    816.0 Assertion failed: isComplete() src/libsrc/ladebug/symbol. 



Performance

  Fix Eventually
    714.0 Is ladebug reopening every command?	    

Thanks for the input.  We will take that into consideration in our
current plan.

Wanfang