public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/17397] i686-w64-mingw32 remote multiprocess debugging: thread.c:1002: internal-error: switch_to_thread: Assertion `inf != NULL' failed.
Date: Fri, 27 Feb 2015 11:45:00 -0000	[thread overview]
Message-ID: <bug-17397-4717-atOL9omNBk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17397-4717@http.sourceware.org/bugzilla/>

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

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at redhat dot com

--- Comment #4 from Pedro Alves <palves at redhat dot com> ---
I suspect this is fixed in more recent GDB.  Could you try mainline?

Also, can you debug GDB a little?  What was the ptid of the thread that
GDB was expecting to find in the thread list, but isn't there?  And why isn't
it there anymore?  The ptid is unfortunately not visible here (frame #6):

...
#4  0x00000000006336b9 in internal_verror (file=<optimized out>, 
    line=<optimized out>, fmt=<optimized out>, ap=ap@entry=0x7fff7cd84ac8)
    at utils.c:803
#5  0x0000000000633762 in internal_error (file=file@entry=0x771a62 "thread.c", 
    line=line@entry=1002, string=<optimized out>) at utils.c:813
#6  0x000000000056a6df in switch_to_thread (ptid=...) at thread.c:1002
#7  0x000000000056b607 in print_thread_info (uiout=0x2233590, 
    requested_threads=0x226f8e0 "1", pid=-1) at thread.c:928
#8  0x00000000004aa601 in mi_cmd_execute (parse=0x2228820)
    at ./mi/mi-main.c:2253
#9  captured_mi_execute_command (context=0x2228820, uiout=0x2233590)
    at ./mi/mi-main.c:1988
#10 mi_execute_command (cmd=0x22701c0 "23-thread-info 1", 
    from_tty=<optimized out>) at ./mi/mi-main.c:2116
...

Please get a backtrace with "set print frame-arguments all".

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


  parent reply	other threads:[~2015-02-27 10:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 13:13 [Bug remote/17397] New: " jerome.gardou at reactos dot org
2015-02-26 19:44 ` [Bug remote/17397] " jerome.gardou at reactos dot org
2015-02-27 10:08 ` jerome.gardou at reactos dot org
2015-02-27 11:45 ` palves at redhat dot com [this message]
2015-02-27 12:01 ` jerome.gardou at reactos dot org
2015-02-27 12:03 ` jerome.gardou at reactos dot org
2015-02-27 14:02 ` jerome.gardou at reactos dot org
2015-02-27 16:48 ` jerome.gardou at reactos dot org
2015-03-19 11:26 ` palves at redhat dot com
2015-04-04 14:59 ` jerome.gardou at reactos dot org
2015-04-07  8:35 ` palves at redhat 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-17397-4717-atOL9omNBk@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).