{"action":"created","issue":{"url":"https://api.github.com/repos/01org/processor-trace/issues/39","repository_url":"https://api.github.com/repos/01org/processor-trace","labels_url":"https://api.github.com/repos/01org/processor-trace/issues/39/labels{/name}","comments_url":"https://api.github.com/repos/01org/processor-trace/issues/39/comments","events_url":"https://api.github.com/repos/01org/processor-trace/issues/39/events","html_url":"https://github.com/01org/processor-trace/issues/39","id":314672890,"number":39,"title":"error: expected tracing enabled event","user":{"login":"vext01","id":604955,"avatar_url":"https://avatars2.githubusercontent.com/u/604955?v=4","gravatar_id":"","url":"https://api.github.com/users/vext01","html_url":"https://github.com/vext01","followers_url":"https://api.github.com/users/vext01/followers","following_url":"https://api.github.com/users/vext01/following{/other_user}","gists_url":"https://api.github.com/users/vext01/gists{/gist_id}","starred_url":"https://api.github.com/users/vext01/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vext01/subscriptions","organizations_url":"https://api.github.com/users/vext01/orgs","repos_url":"https://api.github.com/users/vext01/repos","events_url":"https://api.github.com/users/vext01/events{/privacy}","received_events_url":"https://api.github.com/users/vext01/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2018-04-16T14:21:57Z","updated_at":"2018-04-19T11:15:19Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Hello!\r\n\r\nI've noticed that when I trace user code (using `attr.exclude_kernel = 1`) and there's a system call in the trace, then ptxed will generate en error message upon returning to user-space:\r\n```                                              \r\n$ ptxed --cpu auto, --block-decoder --block:end-on-call --block:end-on-jump \\\r\n            --block:show-blocks --pt ...\r\n...\r\n0000557a22886c5c  mov edi, dword ptr [rdi+0x18]         \r\n0000557a22886c5f  call 0x557a22878f58         \r\n[block]         \r\n0000557a22878f58  jmp qword ptr [rip+0x2f1c7a]         \r\n[block]         \r\n00007fde76ddfe00  mov eax, 0x10         \r\n00007fde76ddfe05  syscall          \r\n[disabled]         \r\n[3ec80, 7fde76ddfe07: error: expected tracing enabled event]         <--------- this\r\n[block]         \r\n00007ffe85dc5a20  jle 0x7ffe85dc5b1d         \r\n[block]         \r\n```\r\n\r\nIs that supposed to happen? If not, I'm wondering if that's a bug in `ptxed`, the Linux kernel I'm using (`4.9.30-2+deb9u5`), or the chip itself?\r\n\r\nAny ideas?"},"comment":{"url":"https://api.github.com/repos/01org/processor-trace/issues/comments/382697938","html_url":"https://github.com/01org/processor-trace/issues/39#issuecomment-382697938","issue_url":"https://api.github.com/repos/01org/processor-trace/issues/39","id":382697938,"user":{"login":"vext01","id":604955,"avatar_url":"https://avatars2.githubusercontent.com/u/604955?v=4","gravatar_id":"","url":"https://api.github.com/users/vext01","html_url":"https://github.com/vext01","followers_url":"https://api.github.com/users/vext01/followers","following_url":"https://api.github.com/users/vext01/following{/other_user}","gists_url":"https://api.github.com/users/vext01/gists{/gist_id}","starred_url":"https://api.github.com/users/vext01/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vext01/subscriptions","organizations_url":"https://api.github.com/users/vext01/orgs","repos_url":"https://api.github.com/users/vext01/repos","events_url":"https://api.github.com/users/vext01/events{/privacy}","received_events_url":"https://api.github.com/users/vext01/received_events","type":"User","site_admin":false},"created_at":"2018-04-19T11:15:19Z","updated_at":"2018-04-19T11:15:19Z","author_association":"CONTRIBUTOR","body":"Hi,\r\n\r\nI copy packet data out of the AUX buffer in chunks, once each time I receive a `PERF_RECORD_SAMPLE`. Once I have stopped tracing and have the whole trace in a separate heap allocated buffer, I then decode the whole lot in one go.\r\n\r\n> Can you reproduce the issue when recording with perf or simple-pt?\r\n\r\nI'll give it a go. I didn't realise `perf record` would store the trace in a format `ptxed` would understand."}}
{"actor":{"display_login":"vext01"}}