[Bug gdb/12905] gdb 7.2 asserts "thread.c:598: internal-error: Assertion `tp' failed." on x86_64-sun-solaris2.10

["tim.mooney at ndsu dot edu" <sourceware-bugzilla@sourceware.org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=12905

tim.mooney at ndsu dot edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|7.2                         |7.4

--- Comment #2 from tim.mooney at ndsu dot edu 2012-04-20 17:16:12 UTC ---
My apologies for taking months to get back to this.

I just tried 7.4 and the exact same issue is still present (line number has
changed though):

$/tmp/gdb /local/gnu/bin/gnome-terminal 
GNU gdb (GDB) 7.4
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-pc-solaris2.10".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /local/gnu/bin/gnome-terminal...done.
(gdb) run
Starting program: /local/gnu/bin/gnome-terminal 
[New LWP 2]
[LWP 2 exited]
thread.c:613: internal-error: Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

thread.c:613: internal-error: 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
Abort (core dumped)




Of interest, after gdb dumps core, the inferior I was trying to run
(gnome-terminal) starts up.

Not that it makes a difference in this case, but I'm using a newer version of
the Sun/Oracle Studio compiler now.  I've upgraded to Studio 12.3.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.