From: DSP Hotline

Subject: 320C30 HLL Debugger Bug List

-------------------------------------------------------------------------------
* RELEASE 4.60 BUGLIST                                                        *
* Update - 02/11/94                                                           *
*                                                                             *
* This file contains a list of bugs in the release 4.xx of the                *
* 320C30 HLL Debugger                                                         *
-------------------------------------------------------------------------------


				Part 1

HLL
-------------------------------------------------------------------------------

5523     V(current)  will fix next release
  The Sun versions of the debuggers, emulators and simulators, do not support    
the "system", "cd" or "dir" commands.


5578     V4.60  will fix in V4.61
  An alias command with a string longer than 76 characters causes problems.      
For example the following take file:

? pc=0
alias l,"echo This is simply a very, very, very long alias of more than 76
 characters."
echo Error here.
? pc=1
alias

produces the following in the command window :

         0x00000000
        Error here.
        Invalid argument
          Alias          Command
        --------         -------
        L            --> echo This is simply a very, very, very long alias of m
ore than 76 chara
         --- Emulator Memory error

There are two bugs:  first, alias command doesn't get the entire
line, only 80 characters, and yet doesn't complain.  And second, once this
"bad" alias occurs you can no longer use E, eval, ?, reset, nor access memory
with the debugger.  Thus ? pc=1 gives an "Invalid argument" error and then
when the take file is complete and the debugger tries to update the screen,
" --- Emulator memory error".  This second problem, at least, goes away if you
use an alias of less than 77 characters.


XDS510WS
-------------------------------------------------------------------------------

5521     V1.00  will fix in V1.01
  The production version of the XDS510WS fails to respond to probe-scsi or       
emurst, nor does it's sd? information display when its attatched Sparc
reboots.
 
Root cause was the device ignored the SCSI bus after recieving a SCSI bus
reset.  The bug also exists in the first production release of the C3x
emulator software for the XDS510WS.

SOLUTION/WORKAROUND : 
 
    Don't power-up the XDS510WS until after the Sparc has completed booting,
    or update ROM.


EMULATOR
-------------------------------------------------------------------------------

5355     V4.60  will fix next release
  On SUN workstation, emu3x using -p 0 fails, attempts to open device at sd4.    


Workaround: Use a different driver other than sd0.


5359     V4.60  will fix next release
  Note: This is a problem on SUN & PC under SunOS and OS/2

The board configuration path and filename specified after the -f option        
is limited to 32 characters including the '\0' end-of-string character.
Longer names are truncated.

This is especially a problem when the OS expands names as in ~user.


Workaround: Don't use long names.


5364     V4.60  will fix next release
  Under the following specific circumstance, the debugger may incorrectly 
calculate the number/size of the packets required to perform a transfer 
across the SCSI bus. This problem will affect both the memory save, MS, 
and LOAD commands.  If the length specified in the MS command, or the 
length of the loaded portion of the file given in the LOAD command is such 
that (length%500)%128>116, then the proper number of WORDS will not be 
saved/loaded. 


Workaround: For MS command - 

         1). break the range of memory specified
             into sizes of appropriate lengths.
          That is  (length%500)%128<=116.

         For LOAD command - 
         
            2). Check the link map from the link of the object file,
          for the size of all loaded (UNITIALIZED sections are not
          loaded) sections to make sure that the section lengths 
          are in bounds, i.e. (length%500)%128>116. 
          
          If the section length exceeds this figure then pad the 
          section to the next 128 word boundary. This may be done 
          by altering the link command file Sections directive for the 
          corresponding "bad" section.

          i.e.

          badsec : { *(badsec)
                  .+= "pad length" ;   } ....


5486     V4.60  will fix in V4.61
  The debugger comes up, but I can't modify memory or registers, nor run.

    CAUSE : User didn't execute emurst with the correct c?x510ws.out
            since powering-up the XDS510WS, but before invoking the debugger.

SOLUTION/WORKAROUND DESCRIPTION : 
    Obviously, make sure to execute emurst with the correct c?x510ws.out
    file prior to invoking the debugger, yet after powering-up the XDS510WS.


5490     V4.60  will fix in V4.61
  The XDS510WS hangs if emu3x is executed on it, but it was initialized,
via emurst, with a file other than c3x510ws.out, such as c4x510ws.out.
SOLUTION/WORKAROUND DESCRIPTION:
    Cycle the power on the XDS510WS and re-emurst with the correct
    c?x510ws.out file or simply have enough sense not to execute a
    debugger on an XDS510WS that is not set up for that device.


EVM
-------------------------------------------------------------------------------

4917     V4.50  will fix next release
  On Version 4.5 of the EVM30 HLL debugger, a delayed branch is executed
correctly however it is shown as a standard branch in the disassembly window.

For example:DBUD     AR3,loop
          is shown as
         DB          AR3,loop


-------------------------------------------------------------------------------
