{"action":"closed","issue":{"url":"https://api.github.com/repos/namhyung/uftrace/issues/53","repository_url":"https://api.github.com/repos/namhyung/uftrace","labels_url":"https://api.github.com/repos/namhyung/uftrace/issues/53/labels{/name}","comments_url":"https://api.github.com/repos/namhyung/uftrace/issues/53/comments","events_url":"https://api.github.com/repos/namhyung/uftrace/issues/53/events","html_url":"https://github.com/namhyung/uftrace/issues/53","id":199750963,"number":53,"title":"need modification in tutorial","user":{"login":"iamwonseok","id":22901131,"avatar_url":"https://avatars.githubusercontent.com/u/22901131?v=3","gravatar_id":"","url":"https://api.github.com/users/iamwonseok","html_url":"https://github.com/iamwonseok","followers_url":"https://api.github.com/users/iamwonseok/followers","following_url":"https://api.github.com/users/iamwonseok/following{/other_user}","gists_url":"https://api.github.com/users/iamwonseok/gists{/gist_id}","starred_url":"https://api.github.com/users/iamwonseok/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iamwonseok/subscriptions","organizations_url":"https://api.github.com/users/iamwonseok/orgs","repos_url":"https://api.github.com/users/iamwonseok/repos","events_url":"https://api.github.com/users/iamwonseok/events{/privacy}","received_events_url":"https://api.github.com/users/iamwonseok/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-01-10T07:30:26Z","updated_at":"2017-01-10T15:45:01Z","closed_at":"2017-01-10T15:45:01Z","body":"When I read a tutorial of function-depth filter part, I was difficult to understand from your assumption.\r\n\r\nI'm attaching the original text as below and marking the bold the part of your assumption that I was confused.\r\n\r\n========== text from tutorial ==========\r\nThe next is function-depth filter. You can use -D or --depth to limit function call depth to be recorded. Below is apply depth-2 filter on the uftrace itself when replay the hello world program. **To make it clearer, I named the binary built with the compiler instrumentation as \"uftrace-pg\" and assume the trace data is in hello.data.** The \"--\" in the command line is to tell the option parser that it's the end of the option. For simplicity, I omitted the output of replaying hello world from the uftrace-pg:\r\n$ uftrace -D 2 -- uftrace-pg replay -d hello.data\r\n========== text from tutorial ==========\r\n\r\nThe confusion came from how to create hello.data. Even if uftrace can record the trace data to specific directory and you discussed at the front of tutorial, there is no kindly guideline to store tracing data to specific directory.\r\n\r\nWhen I was executed \"uftrace record hello -d hello.data\" at the first time, because I followed replay command in the example. After I executed the command, only “uftrace.data” was created. The reason made me confused. Anyway, I found the way to store data with directory name. There are two ways to use “uftrace -d hello.data record hello” or “uftrace record -d hello.data hello”.\r\n\r\nThe command “uftrace record hello -d hello.data” is no effect to directory’s name, Is it your intention? or is the problem in parsing the argument in uftrace? \r\n\r\nAnyway, the goal of the paragraph is to show feature of function-depth tracing, isn’t it? If so, it would be better to use a simpler example for user like me (newbie) instead of uftrace-pg and hello.data. You know, the newbie like me, expects examples in the tutorial will run without modification."}}
{"actor":{"display_login":"namhyung"}}