X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=ltrace.conf.5;h=1efd4fc98ddd1dc54c6c6a8d41b9974e7f49d97c;hb=8b7c2b422eb5a79348ab56c8e8ce80a9ab1b62b9;hp=bdf0ceb5fba3001eb0a5d9e1b7d848d038eebe28;hpb=e6c25f6799825812e2b87990333c649ba796f600;p=platform%2Fupstream%2Fltrace.git

diff --git a/ltrace.conf.5 b/ltrace.conf.5
index bdf0ceb..1efd4fc 100644
--- a/ltrace.conf.5
+++ b/ltrace.conf.5
@@ -30,8 +30,9 @@ Ltrace needs this information to display function call arguments.
 
 Each line of a configuration file describes at most a single item.
 Lines composed entirely of white space are ignored, as are lines
-starting with semicolon character (comment lines).  Described items
-can be either function prototypes, or definitions of type aliases.
+starting with semicolon or hash characters (comment lines).  Described
+items can be either function prototypes, or definitions of type
+aliases.
 
 .SH PROTOTYPES
 
@@ -224,7 +225,7 @@ such type, and later just use that name:
 .SH RECURSIVE STRUCTURES
 
 Ltrace allows you to express recursive structures.  Such structures
-are expanded to the depth described by the parameter -A.  To declare a
+are expanded to the depth described by the parameter \-A.  To declare a
 recursive type, you first have to introduce the type to ltrace by
 using forward declaration.  Then you can use the type in other type
 definitions in the usual way:
@@ -404,7 +405,7 @@ ltrace configuration line.
 .br
 .B struct\fR S1 func_struct\fB(int \fRa\fB, struct \fRS2\fB, double \fRd\fB);
 .RS
-.B struct(float,char,char)\fR func_struct_2\fB(int, struct(string(array(char, \fR6\fB)),float), double);
+.B struct(float,char,char)\fR func_struct\fB(int, struct(string(array(char, \fR6\fB)),float), double);
 .RE
 
 .SH AUTHOR