public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jerome.gardou at reactos dot org" <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 12:01:00 -0000	[thread overview]
Message-ID: <bug-17397-4717-n2dXTHegRo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17397-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from jerome.gardou at reactos dot org ---
Created attachment 8151
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8151&action=edit
GDB 7.9 crash log

I tried with GDB 7.9, with debugging (-g3) enabled and disabled optimizations.
There is still an assert failing, but quite different this time. I don't know
if this is a different symptom of the same bug, or another one.

Here is the log triggering the crash.

I will try to compile mainline as soon as I can.

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


  parent reply	other threads:[~2015-02-27 12:00 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
2015-02-27 12:01 ` jerome.gardou at reactos dot org [this message]
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-n2dXTHegRo@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).