This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Possibly a bug in glibc around the getrandom(2) implementation.
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Marcin Mielniczuk <marmistrz dot dev at zoho dot eu>, libc-help at sourceware dot org
- Date: Fri, 14 Jul 2017 10:02:57 -0400
- Subject: Re: Possibly a bug in glibc around the getrandom(2) implementation.
- Authentication-results: sourceware.org; auth=none
- References: <00dbbfa7-05ce-9d3f-d32b-e519c8c0dfc3@zoho.eu>
On 07/14/2017 09:11 AM, Marcin Mielniczuk wrote:
> My environment: Arch Linux, kernel 4.9.36-1-lts, glibc 2.25, Python 3.6.1 (and 3.7.0 from git).
> The same error was reproduce on a similar setup but with kernel 4.11.5-1-ARCH.
>
> Do you have any ideas, what to do next?
Use gdb. It's the one tool your missing from all of the steps you've done.
You actually have to get down the machine level and see what is happening
to the stack pointer at the point of failure and why it's failing. You need
to match that up with the process memory map e.g. /proc/self/maps and catch
what is going on.
--
Cheers,
Carlos.