This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: LIBC_PROBE and locks
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 16 Nov 2015 23:20:30 -0500
- Subject: Re: LIBC_PROBE and locks
- Authentication-results: sourceware.org; auth=none
- References: <564A1849 dot 1040304 at redhat dot com>
On 11/16/2015 12:54 PM, Florian Weimer wrote:
> Is it okay to call LIBC_PROBE while internal locks are held? Or could
> this result in deadlocks by itself? (I'm aware that the arguments are
> always evaluated.)
How would it cause deadlocks? The external observer, say systemtap or
gdb, are outside of the process and should not modify the state of the
process in such a way as to cause a deadlock. Under what conditions might
the evaluation of the arguments cause a deadlock?
Cheers,
Carlos.