This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gdb/400: remote-sim.h doesn't handle threads or multi-cpu targets



>Number:         400
>Category:       gdb
>Synopsis:       remote-sim.h doesn't handle threads or multi-cpu targets
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 06 19:08:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
Simulators such as PSIM are capable of modeling multi-cpu operating environment architectures and multi-threaded virtual environment architectures.

The remote-sim.h interface does not provide a mechanism for accessesing such threads / cpus.

Care will be needed as simulators have ``strange'' scheduler behavour.  A sim will often use deterministic fine grain scheduling to model concurrency (one cpu/cycle per thread at a time).  This fine grain scheduling could cause a number of problems:

- when gdb tells the sim to step, the sim will execute one instruction for the current cpu/thread and then switch to the next cpu

- gdb will find that it can't step a specific thread - the sim will ignore it.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]