Fix: generate header missing echo -e for escape chars
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Tue, 17 Apr 2012 14:50:12 +0000 (10:50 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Tue, 17 Apr 2012 14:52:48 +0000 (10:52 -0400)
commitfa73137a9984cd453fe895cca204f9d73291c1b2
tree5d60d950c1e848c8595dd537d0d2b757b2ae720c
parentd28686c15dba4a8080a2217c92411b93875068dc
Fix: generate header missing echo -e for escape chars

"why is the -e needed ? What was the experienced oddness ?"

   The \n wasn't getting evaluated to a newline and was being inserted
into the header file as '\n'

   From man echo(1):

       If -e is in effect, the following sequences are recognized:

       \\     backslash

       \a     alert (BEL)

       \b     backspace

       \c     produce no further output

       \e     escape

       \f     form feed

       \n     new line

       \r     carriage return

       \t     horizontal tab

       \v     vertical tab

Suggested-by: Ryan Kyser <Ryan.Kyser@jci.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
instrumentation/syscalls/lttng-syscalls-generate-headers.sh
This page took 0.026532 seconds and 4 git commands to generate.