From fa73137a9984cd453fe895cca204f9d73291c1b2 Mon Sep 17 00:00:00 2001 From: Mathieu Desnoyers Date: Tue, 17 Apr 2012 10:50:12 -0400 Subject: [PATCH] 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 Signed-off-by: Mathieu Desnoyers --- instrumentation/syscalls/lttng-syscalls-generate-headers.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/instrumentation/syscalls/lttng-syscalls-generate-headers.sh b/instrumentation/syscalls/lttng-syscalls-generate-headers.sh index 5eddb274..046dc067 100644 --- a/instrumentation/syscalls/lttng-syscalls-generate-headers.sh +++ b/instrumentation/syscalls/lttng-syscalls-generate-headers.sh @@ -59,7 +59,7 @@ if [ "$CLASS" = integers ]; then NRARGS=0 -echo \ +echo -e \ 'SC_DECLARE_EVENT_CLASS_NOARGS(syscalls_noargs,\n'\ ' TP_STRUCT__entry(),\n'\ ' TP_fast_assign(),\n'\ -- 2.34.1