Paran Lee

I tested `thrd_*` on GCC, Clang but i need to examining the evidence for the proof. # ISO `thred.h` and `thrd_*` We can find n1548 standard [[1]](https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1548.pdf). > 7.25.5 Thread...

This visualization example looks good to me.  - https://vizhub.com/srinivasjavvadi/86280477e61c4a199c38d3faa6ff9503?edit=files&file=data-example.json

ASAN detects 120 times on `/home/kim/uftrace/utils/tracefs.c:27`. ``` grep "/home/kim/uftrace/utils/tracefs.c:27" runtest.log | wc -l 120 ```

When we do `find_tracing_dir()`, there is `fopen()` but not `fclose()`.

I have solved that issue with remove cloned uftrace directory and re-clone uftrace repo and then build. I guess some files are privileged so cannot modified. I think doing `make...

@honggyukim No. present make clean dose not solve freeze. So I remove the local repository and I did the re-cloned uftrace repo and build. I'll have to do a little...

Thanks for [the confirmation](https://github.com/namhyung/uftrace/issues/1738#issuecomment-1603613958), @namhyung. In Xen project, They are using [Gitlab CI](https://gitlab.com/xen-project/xen/-/blob/staging/automation/gitlab-ci/test.yaml) by mirroring the repository on [each arch](https://gitlab.com/xen-project/xen/-/tree/staging/automation/scripts). What do you think of this? They are also using...

I find another examples on Github Actions. - https://support.circleci.com/hc/en-us/articles/17034320054811-How-to-run-arm64-docker-images ```yml version: 2.1 jobs: test: machine: image: ubuntu-2004:2022.04.1 resource_class: arm.medium steps: - checkout - run: name: Start arm docker container command:...

multi arch docker buildx example - https://buildabetterworld.tistory.com/178 - activate buildx - https://80000coding.oopy.io/54dc871d-30c9-46cb-b609-2e8831541b5e ```sh $ docker buildx build --platform linux/amd64,linux/arm64,linux/arm/v7 -t username/demo:latest --push . ```

@honggyukim `022 filter_kernel` runtest in x64 also failed. And ASAN tell me there is memory leaks. Is it better to create a separate issue for a different architecture? ``` =================================================================...