[Bug libc/19988] New: Chromium browser hits assertion when build on glibc trunk

["markus at trippelsdorf dot de" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 19988
           Summary: Chromium browser hits assertion when build on glibc
                    trunk
           Product: glibc
           Version: 2.24
               URL: https://bugs.chromium.org/p/chromium/issues/detail?id=
                    604652
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: markus at trippelsdorf dot de
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

A recent header change causes the Chromium browser to hit an 
assertion on startup  (base/rand_util_posix.cc:54):

[23620:23620:0419/105518:FATAL:rand_util_posix.cc(54)] Check failed: success. 
#0 0x555556474a2e base::debug::StackTrace::StackTrace()
#1 0x55555648b0e7 logging::LogMessage::~LogMessage()
#2 0x5555564a7d4c base::RandBytes()
#3 0x555557029feb mojo::edk::NodeController::NodeController()
#4 0x55555701f928 mojo::edk::Core::GetNodeController()
#5 0x55555701f985 mojo::edk::Core::SetIOTaskRunner()
#6 0x55555701e732 mojo::edk::InitIPCSupport()
#7 0x55555a78def1 IPC::(anonymous namespace)::IPCSupportInitializer::Init()
#8 0x55555a78dff8 IPC::ScopedIPCSupport::ScopedIPCSupport()
#9 0x55555acd561c content::ChildThreadImpl::Init()
#10 0x555559799b88 content::RenderThreadImpl::RenderThreadImpl()
#11 0x555559799fbf content::RenderThreadImpl::Create()
#12 0x5555597bd50d content::RendererMain()
#13 0x5555564445e3 content::ContentMainRunnerImpl::Run()
#14 0x555556443c6c content::ContentMain()
#15 0x555556029fdd ChromeMain
#16 0x7ffff601af11 __libc_start_main
#17 0x555556029e5a _start

https://chromium.googlesource.com/chromium/src/base/+/master/rand_util_posix.cc

Building with glibc-2.23 branch headers "fixes" the issue.

Haven't looked deeper yet. 
Any idea what header change might cause this issue?

See also: https://bugs.chromium.org/p/chromium/issues/detail?id=604652

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