Changes between Version 1 and Version 2 of Developer/Projects/Open/ImproveGDBSim


Ignore:
Timestamp:
Mar 20, 2016, 12:24:10 AM (3 years ago)
Author:
Joel Sherrill
Comment:

Typos and add more

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Projects/Open/ImproveGDBSim

    v1 v2  
    1919to gdb/remote-sim.c and sim/common has an inferior also to
    2020gdb/remote-sim.c which the SIS should sit under. Without this the run
    21 command is broken. We have hacked around this for gdb-7.11 by adding back
    22 the removed gdb code (run.c). This is not a sustainable solution. All
    23 the current SIS inferior calls, eg sim_open, sim_close, sim_read etc,
    24 need to be moved over. This requires the SIS's internal view of memory
    25 needs to match the sim/common's view so the SIS view and the GDB vewi,
     21command is broken. We have hacked around this for gdb-7.11 by adding back the removed gdb code (run.c). This is not a sustainable solution. All the current SIS inferior calls, eg sim_open, sim_close, sim_read etc., need to be moved over. This requires the SIS's internal view of memory
     22needs to match the sim/common's view so the SIS view and the GDB view,
    2623which is the user's view, are the same. There are a number of other
    2724issues such as printf which was hacked in a recent gdb-7.11 patch.
     
    3835After this there are other simulators to look at, specifically the
    3936aarch64 one and RTEMS. Having the aarch64 run an RTEMS app would be we
    40 nice. It only needs to do as far and a few instructions or maybe a 32bit
    41 build of RTEMS which the aarch64 should support.
     37nice. It only needs to do as far and a few instructions or maybe a 32-bit build of RTEMS which the aarch64 should support.
    4238
    43 There are also a number of Windows related issues in the simulators that
    44 would be nice to clean up.
     39There are also a number of Windows related issues in the simulators that would be nice to clean up.
     40
     41The arm simulator has issues with some ARM CPU models. These could be single instructions issues or missing entire capabilities. For example, is a single Thumb instruction missing or is Thumb not supported at all. The first step is identifying what the simulator supports fully and adding configurations to the arm/gdbarmsim BSP to use. The second step is fixing the cases where one or a few instructions are not supported and making gdbarmsim configurations to use these models. For ARM capabilities completely unsupported, we just can ignore them for the purpose of gdbarmsim. Adding them is beyond the scope of this project.
     42
     43Adding tracing/coverage support to the common simulator framework and using the output in covoar. This will let the RTEMS Coverage framework execute programs on gdb simulators and produce coverage reports.
    4544
    4645