Quick-start guide should include '-k'

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Follow quick-start guide 
2. Run ./strace -o hello.out ./hello
3. Wonder why hello.out does not contain stack traces and instead looks like 
vanilla strace output.
4. Bang on source code for a while
5. Discover that '-k' is required to enable stack trace output

What version of the product are you using? On what operating system?
Current master (acb9665) on Linux i386.

Original issue reported on code.google.com by amdragon@gmail.com on 22 Sep 2013 at 11:25

[GoogleCodeExporter]

Hi, after using following steps :-

./strace -k -o hello.out ./hello
python scripts/pretty_print_strace_out.py hello.out --trace

I am not getting complete backtrace containing filename and functions called.

output is:-

write(1, "Hello world\n", 12)           = 12
  > write() [/lib/x86_64-linux-gnu/libc-2.15.so]
write(1, "foo\n", 4)                    = 4
  > write() [/lib/x86_64-linux-gnu/libc-2.15.so]
write(1, "bar\n", 4)                    = 4
  > write() [/lib/x86_64-linux-gnu/libc-2.15.so]
write(1, "bar again\n", 10)             = 10

It has no information about filename and functions called.

I am also attaching source file and .py file

Original comment by rahulz2...@gmail.com on 26 Jul 2014 at 4:15

Attachments:

• hello.c
• pretty_print_strace_out.py