public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dennis.wang at nrl dot navy.mil" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/11362] Debugging from CDT raises "thread.c:79: internal-error: inferior_thread: Assertion `tp' failed."
Date: Fri, 01 Jul 2011 20:41:00 -0000	[thread overview]
Message-ID: <bug-11362-4717-G0N9iDkYLb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11362-4717@http.sourceware.org/bugzilla/>

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

dennis.wang at nrl dot navy.mil changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dennis.wang at nrl dot
                   |                            |navy.mil
            Version|7.0                         |7.2

--- Comment #4 from dennis.wang at nrl dot navy.mil 2011-07-01 20:40:36 UTC ---
I see this same bug in version 7.2  I am running gdb on a Ubuntu 11.04 system
and connecting to a PC running MINGW.  The output below is from the Ubuntu box.
------------

GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 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 "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.....

Reading symbols from /home/wang/Documents/RTEMS/tests/stanford...done.
(gdb) target extended-remote 132.250.xxx.xxx:2222
Remote debugging using 132.250.xxx.xxx:2222
0x00000000 in ?? ()
(gdb) load
Loading section .text, size 0xf740 lma 0x40000000
Loading section .data, size 0x820 lma 0x4000f740
Start address 0x40000000, load size 65376
Transfer rate: 8 KB/sec, 271 bytes/write.
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y

/build/buildd/gdb-7.2/gdb/thread.c:79: internal-error: 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

/build/buildd/gdb-7.2/gdb/thread.c:79: internal-error: inferior_thread:
Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

-- 
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.


       reply	other threads:[~2011-07-01 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11362-4717@http.sourceware.org/bugzilla/>
2011-07-01 20:41 ` dennis.wang at nrl dot navy.mil [this message]
2014-02-16 18:28 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org
2010-03-09 17:29 [Bug threads/11362] New: " gaknar at gmail dot com
2010-03-09 17:31 ` [Bug threads/11362] " gaknar at gmail dot com
2010-03-09 17:40 ` gaknar at gmail dot com
2010-03-09 18:03 ` gaknar at gmail dot com

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=bug-11362-4717-G0N9iDkYLb@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).