On 11/11/24 09:02, Richard Henderson wrote:
On 11/11/24 06:59, Richard Henderson wrote:
On 10/23/24 16:47, J. Neuschäfer wrote:
This aligns with strace, and is very useful when tracing multi-threaded
programs. The result is the same in single-threaded programs.
See also "-D log.%d -d tid -str
On 11/11/24 06:59, Richard Henderson wrote:
On 10/23/24 16:47, J. Neuschäfer wrote:
This aligns with strace, and is very useful when tracing multi-threaded
programs. The result is the same in single-threaded programs.
See also "-D log.%d -d tid -strace" which will split the output into per-tid
On 10/23/24 16:47, J. Neuschäfer wrote:
This aligns with strace, and is very useful when tracing multi-threaded
programs. The result is the same in single-threaded programs.
See also "-D log.%d -d tid -strace" which will split the output into per-tid
files.
gettid() requires the _GNU_SOURCE
On Thu, Oct 24, 2024 at 01:47:31AM +0200, J. Neuschäfer wrote:
> This aligns with strace, and is very useful when tracing multi-threaded
> programs. The result is the same in single-threaded programs.
>
> gettid() requires the _GNU_SOURCE feature test macro, so it might be
> unavailable in rare cas
This aligns with strace, and is very useful when tracing multi-threaded
programs. The result is the same in single-threaded programs.
gettid() requires the _GNU_SOURCE feature test macro, so it might be
unavailable in rare cases. I don't expect it to be a problem though,
because it's implemented b
