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/673: GDB/MI wrong state(inferior is stopped)


>Number:         673
>Category:       gdb
>Synopsis:       GDB/MI wrong state(inferior is stopped)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 26 12:18:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     alain@qnx.com
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
GDB/MI does not sent the oob say the target is "stopped", for example:

(gdb)
-thread-select 2
...
-stack-select-frame 0
...
-exec-next
^running
&"Cannot find bounds of current funtion\n"
^error,msg="Cannot find bounds of current function\n"
(gdb)

Altought the "^running" was issued an error is thrown, now it is
unclear to me the target is "stopped" or still actually "running" even
if there was an error.  Maybe GDB/MI should have sent a:
^stopped

>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]