From daf7880caf129797a3ab4873d675d2362528b0cb Mon Sep 17 00:00:00 2001 From: Alain Magloire Date: Mon, 21 Oct 2002 02:56:04 +0000 Subject: [PATCH] update. --- debug/org.eclipse.cdt.debug.mi.core/ChangeLog | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/debug/org.eclipse.cdt.debug.mi.core/ChangeLog b/debug/org.eclipse.cdt.debug.mi.core/ChangeLog index 487ca6f7693..fb37a130778 100644 --- a/debug/org.eclipse.cdt.debug.mi.core/ChangeLog +++ b/debug/org.eclipse.cdt.debug.mi.core/ChangeLog @@ -1,3 +1,21 @@ +2002-10-20 Alain Magloire + + Eclipse provides plugins a way to trace by having an .options file, + this mechanism is use to print out the mi exchange between gdb + and the plugin. To enable this in the debug launch one must enable + "tracing" and set for the "org.eclipse.debug.mi.core/debug" to true. + But one problem, the console will simply blow taking down eclipse, + for big MI line response, say 4k length, for example asking the children + of "char buffer[4096]", -var-list-children varxx. + This seem only to happen in Eclipse-gtk or Eclipse-motif + on GNU/Linux, so it will be break in smaller chunks to give a chance to + the console. + + * .options: Set debug to true. + * src/.../core/MIPlugin.java (debugLog): Break the log line in small chuncks of 100. + * src/.../MISession.java (postCommand): Print the gdb/mi command. + * src/.../RxThread.java (run): Print gdb/mi responses. + 2002-10-20 Alain Magloire -data-write-register-values is not in the texinfo manual but implemented in