[Bug c++/23387] New: thread.c:93: internal-error: struct thread_info *inferior_thread(): Assertion `tp' failed.

[hellochen19970916 at gmail dot com]

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

Bug ID: 23387
Summary: thread.c:93: internal-error: struct thread_info
*inferior_thread(): Assertion `tp' failed.
Product: gdb
Version: 8.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
Assignee: unassigned at sourceware dot org
Reporter: hellochen19970916 at gmail dot com
Target Milestone: ---

Starting program: /Users/dawson/Github/C++/a.out
Unable to find Mach task port for process-id 6719: (os/kern) failure (0x5).
(please check gdb is codesigned - see taskgated(8))
(gdb) y
Undefined command: "y". Try "help".
(gdb) n
The program is not being run.
(gdb) run
thread.c:93: internal-error: struct thread_info *inferior_thread(): Assertion
`tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

thread.c:93: internal-error: struct thread_info *inferior_thread(): Assertion
`tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
[1] 6717 abort (core dumped) gdb a.out

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Target| |*-*-darwin*
CC| |tromey at sourceware dot org

[tromey at sourceware dot org]

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

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Dawson from comment #0)

Post by hellochen19970916 at gmail dot com
Starting program: /Users/dawson/Github/C++/a.out
Unable to find Mach task port for process-id 6719: (os/kern) failure (0x5).

Is your gdb code-signed?

You can check by running "codesign -d /path/to/gdb".
If it is not signed it will say something like:
/path/to/gdb: code object is not signed at all

But if it is signed it will say something like:
Executable=/path/to/gdb


This is probably a dup of bug#23340.

[hellochen19970916 at gmail dot com]

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

--- Comment #2 from Dawson <hellochen19970916 at gmail dot com> ---
Sorry my labtop is macbook Pro and I tried to use the command
"/path/to/gdb: No such file or directory"

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-07-13
Ever confirmed|0 |1

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Dawson from comment #2)

Post by hellochen19970916 at gmail dot com
Sorry my labtop is macbook Pro and I tried to use the command
"/path/to/gdb: No such file or directory"

Sorry. I did not mean literally type "/path/to/gdb". Instead,
what I meant is that you should find your gdb executable, and then
examine it with codesign -d.

For example, in my case, the path is /usr/local/bin/gdb.
Yours may well be something else. You can usually find out
with "which gdb" in the shell.