public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tedheadster <tedheadster@gmail.com>
To: gentoo-user@lists.gentoo.org, kitware@kitware.com
Subject: [gentoo-user] cmake 3.16.5 Segmentation Violation
Date: Wed, 3 Jun 2020 12:28:52 -0400	[thread overview]
Message-ID: <CAP8WD_aVGa2=iNMD+yMv=mf=ATzYbWEJ_mGZQvHYjMkuk9fq6w@mail.gmail.com> (raw)

I am getting a segmentation violation when running a recompiled
'cmake'. I rebuilt with debugging symbols; here are the results:

/var/tmp/portage/dev-util/cmake-3.16.5/image/usr/bin # gdb ./cmake
GNU gdb (Gentoo 9.1 vanilla) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
...
Reading symbols from ./cmake...
(gdb) run --version
Starting program:
/var/tmp/portage/dev-util/cmake-3.16.5/image/usr/bin/cmake --version
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
cmake version 3.16.5

CMake suite maintained and supported by Kitware (kitware.com/cmake).

Program received signal SIGSEGV, Segmentation fault.
0xb7de7296 in uv_loop_close (loop=0x0) at
/usr/src/debug/dev-libs/libuv-1.35.0/libuv-1.35.0/src/uv-common.c:757
757       if (uv__has_active_reqs(loop))
(gdb) up
#1  0x0053fab4 in main (ac=<optimized out>, av=0xb09a60)
    at /var/tmp/portage/dev-util/cmake-3.16.5/work/cmake-3.16.5/Source/cmakemain.cxx:706
706       uv_loop_close(uv_default_loop());
(gdb) up
Initial frame selected; you cannot go up.
(gdb)


Who can I work with to debug this?

- Matthew


             reply	other threads:[~2020-06-03 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 16:28 tedheadster [this message]
2020-06-03 17:42 ` [gentoo-user] cmake 3.16.5 Segmentation Violation David Haller
2020-06-03 17:50   ` tedheadster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP8WD_aVGa2=iNMD+yMv=mf=ATzYbWEJ_mGZQvHYjMkuk9fq6w@mail.gmail.com' \
    --to=tedheadster@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=kitware@kitware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox