Examining the command that runs the debuggee and corresponding
answers.
GNU gdb log
-----------
gdb DEBUG 100-interpreter-exec console "run"
gdb DEBUG 100^running
GNU gdb answers the "run" command with a RESULT-RECORD.
gdb/MI documentation on RESULT-RECORD:
`"^running"'
The asynchronous operation was successfully started. The target is
running.
Apple gdb log
-------------
gdb DEBUG 100-interpreter-exec console "run"
gdb DEBUG =rerun
gdb DEBUG 100^done,time={...}
Apple gdb answers the "run" command with a "rerun" NOTIFY-ASYNC-OUTPUT
record followed by a RESULT-RECORD.
gdb/MI documentation at:
http://developer.apple.com/library/mac/#documentation/developertools/gdb/gdb/gdb_25.html#SEC244
`"^done" [ "," RESULTS ]'
The synchronous operation was successful, `RESULTS' are the return
values.
Issues
------
* It is not clear what is the meaning of "rerun" in the
Apple gdb NOTIFY-ASYNC-OUTPUT record.
* There is no RESULTS in the gdb Apple RESULT-RECORD.
* The information that the "Program exited normally" is entirely
missing from the log file
Porting pyclewn to the changes made by Apple on gdb/MI and to the way
Apple has interpreted the gdb/MI specification, is not a
straightforward task. One way to do it is to run gdb with the 'mi'
interpreter and test manually each one of the commands used by
pyclewn. Those commands are mostly all the subclasses of OobGdbCommand
in gdbmi.py.
--
Xavier
Les Chemins de Lokoti: http://lokoti.alwaysdata.net
------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and publish
your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general
