dead-lock in glibc
Thu Mar 16 14:28:00 GMT 2017
On Thu, Mar 16, 2017 at 2:30 AM, Joël Krähemann <email@example.com> wrote:
> Thank you for the hints. If you need additional information please let me know.
What would be invaluable would be a program that demonstrates, using
the APIs, the same behaviour outside of the interactive environment
you were using. I know that's a tall order, but usually until someone
drives the problem complexity down a bit we can't easily look at the
In some areas we have made progress to simplify this, for example we
have an API tracer for the malloc family of functions that allows
users to trace an API sequence and replay it in a simulator to attempt
to reproduce a failure. When we extend our tracing to enough APIs we
might be able to one day just get a "API trace" from you and replay it
to observe the same behaviour on our end.
Thanks for the feedback.
More information about the Libc-help