From: cuz <cuz@b7a2c559-68d2-44c3-8de9-860c34a00d81>
Date: Mon, 17 Mar 2003 21:48:37 +0000 (+0000)
Subject: Fixed the comments
X-Git-Tag: V2.12.0~1661
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=93382b722953fca32a118aed7d206b2a658eb9cc;p=cc65

Fixed the comments


git-svn-id: svn://svn.cc65.org/cc65/trunk@2032 b7a2c559-68d2-44c3-8de9-860c34a00d81
---

diff --git a/include/dbg.h b/include/dbg.h
index 21cf3da5d..4749b18be 100644
--- a/include/dbg.h
+++ b/include/dbg.h
@@ -38,12 +38,9 @@
  * used for the debugger are quite usable even in another context, they
  * are declared here.
  *
- * To use the debugger, just call DbgStart in your application. This will
- * clear the screen and startup the debugger with the program counter
- * pointing to the next instruction after the call to DbgStart. Once DbgStart
- * has been executed, the debugger will also catch any BRK opcode. Use the
- * BREAK function declared below to insert additional breakpoints into your
- * code.
+ * To use the debugger, just call DbgInit in your application. Once it has
+ * been called, the debugger will catch any BRK opcode. Use the BREAK macro 
+ * defined below to insert breakpoints into your code.
  *
  * There are currently a lot of things that cannot be debugged, graphical
  * applications are an example. The debugger does not save your screen
@@ -64,7 +61,7 @@
 
 
 /*****************************************************************************/
-/*			      Utuility functions			     */
+/*     	       	       	       Utility functions			     */
 /*****************************************************************************/
 
 
@@ -114,7 +111,7 @@ void __fastcall__ DbgInit (unsigned unused);
  * next brk encountered.
  */
 
-#define BREAK()	       	__asm__ ("\tbrk")
+#define BREAK()	       	__asm__ ("brk")
 /* Use this to insert breakpoints into your code */
 
 
@@ -124,3 +121,4 @@ void __fastcall__ DbgInit (unsigned unused);
 
 
 
+