[Bug gdb/19676] New: gdb fails with assert error if /proc is not mounted

["lsorense at csclub dot uwaterloo.ca" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 19676
           Summary: gdb fails with assert error if /proc is not mounted
           Product: gdb
           Version: 7.10
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: lsorense at csclub dot uwaterloo.ca
  Target Milestone: ---

I was trying to run gdb in a chroot with debian sid armhf and kept getting a
strange assertion error.  Downgrading gdb from 7.10 to 7.7 (from Debian jessie)
made the problem go away.  I eventually realized that it was trying to somehow
determine if the process was running or not so I tried mounting /proc which I
generally don't bother to do in my chroots and never needed to before, and then
the problem vanished.

Trying to run gdb 7.10 without /proc mounted gives:

(gdb) run
Starting program: /usr/bin/python3.5 /usr/bin/nosetests -s -v -A not\ network\
and\ not\ disabled
pandas.io.tests.test_pytables:pandas.io.tests.test_pytables.TestHDFStore.test_append_frame_column_oriented
/build/gdb-eSlPCn/gdb-7.10/gdb/linux-thread-db.c:1675: internal-error:
find_new_threads_once: Assertion `!target_has_execution || thread_db_use_events
()' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

With /proc mounted it just works.

If gdb is going to insist on /proc being mounted to work now, perhaps it could
say so clearly instead of blowing up with an assertion.  Better yet it should
work without /proc like it used to.

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