RE: opcontrol sh: write error: Invalid argument
Andrew Jones <[email protected]>
| Newsgroups | gmane.linux.oprofile |
|---|---|
| Message-ID | <[email protected]> |
> Hi, > > Thanks for the output. The output above looks to match up with opcontrol do_param_setup(): > > if test "$KERNEL_SUPPORT" = "yes" -a -f $MOUNT/backtrace_depth; then > set_param backtrace_depth $CALLGRAPH > > However, the "test yes = yes" doesn't match up with the verion I have. Which specific versions of the kernel and oprofile are you using. Do you have pointers to the specific sources for those? > > -Will Hi Will, Sorry to double post. I have a couple of bytes of extra info: 1. Regarding the "sh: write error: Invalid Argument" message: Jian Peng, in this post, appears to be having this exact same symptom: http://permalink.gmane.org/gmane.linux.oprofile/9406 Later on in that same thread, Maynard said that: "OProfile should "work" in spite of the non-support of callgraph in the kernel." Question: Can I ignore that "Invalid argument" error? 2. Regarding the "Failed to exec opjitconv: No such file or directory" message: In my daemon/init.c, opjitconv_path is equal to: /home/andrew/ex7/output/apps/oprofile_all/usr/bin//opjitconv at runtime. I guess this is derived from my --prefix. If I ignore this error, I am still able to successfully do profiling anyway. So is it safe to ignore this error too? Thanks so much for your help!!! Regards, Andrew ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ oprofile-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oprofile-list