This is the mail archive of the glibc-bugs@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]

[Bug libc/25201] __libc_fork: parent thread stack corruption while looping through 'allp' for calling parent_handler


https://sourceware.org/bugzilla/show_bug.cgi?id=25201

--- Comment #2 from Matthew Qvap <vibrysec at gmail dot com> ---
(In reply to Andreas Schwab from comment #1)
> The atfork handler handing has been refactored in version 2.28 (commit
> 27761a1042).  Does the crash still happen?

it happened once (per thousands installations), the only thing I can look at is
core file from that event - this is what I based bug report.

would the things described above, be able to happen on code prior to 2.28
refactor (I mean did You see the stack looking simillar)?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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