This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Could you kindly explain this modification about pthread_cond_destroy?

From: Florian Weimer <fweimer at redhat dot com>
To: honan li <sayibobo at gmail dot com>
Cc: libc-help at sourceware dot org
Date: Mon, 27 Nov 2017 13:03:23 +0100
Subject: Re: Could you kindly explain this modification about pthread_cond_destroy?
Authentication-results: sourceware.org; auth=none
References: <CA+xL5a-X4U0Ob-gUkfo87ox9kY85W8c-QKVXd7H12r0hP5SMVg@mail.gmail.com>

On 11/27/2017 08:52 AM, honan li wrote:

But back to our issue, on the Qualcomm platform we are working on,
there are many places invoking pthread_cond_destroy, but after each
pthread_cond_destroy, thread or even the process would exit, and at
least for now it seems working all right on glibc2.20. Could you
kindly explain what is the potential risk of the case?


I'm not sure if I understand this question.

It results in undefined behavior. Your application could crash, hang,or even exhibit silent memory corruption, resulting in incorrect results.


Thanks,
Florian

Follow-Ups:
- Re: Could you kindly explain this modification about pthread_cond_destroy?
  - From: Adhemerval Zanella

References:
- Could you kindly explain this modification about pthread_cond_destroy?
  - From: honan li

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]