Hi Rob, On Tue, Dec 6, 2011 at 3:33 PM, Rob wrote: > gdb commands such as 'command' , 'define' and 'end' result in an error > message 'Illegal command in pyclewn'.
This is because some CLI commands, such as `if', `when' and `define', are not valid with gdb/MI, and pyclewn uses gdb/MI to run the gdb commands. But it is much more convenient (IMHO) to write the 'define' and 'command' sequences in a Vim temporary buffer and source the corresponding file with the gdb 'source' command. You can then also refine the implementation of these commands later during the session and reload them with a new 'source' command (which is already in Vim command line history), or store them in a file for later re-use. > If I include a newline inside a quoted string for 'printf', the > newline is converted when echoing the command as well as in the > output: > > :Cprintf \"%i %i\n\", i, j > > prints to the (clewn)_console: > > > gdb) printf "%i %i > ", i, j > 0 0 > > As it does if you add another escape ie. '\\n'. Yes, I can reproduce it on pyclewn 7.2. Curiously, this is fixed in the development version. I will try to track down which change fixed it. Meanwhile I can send you a tarball of the development version I you want. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
