From: Michael Snyder <msnyder@vmware.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: New testsuite errors with gdbserver (remote)
Date: Thu, 17 Feb 2011 02:08:00 -0000 [thread overview]
Message-ID: <4D5C8312.4030701@vmware.com> (raw)
In-Reply-To: <4D5C7552.4010708@vmware.com>
Michael Snyder wrote:
> Michael Snyder wrote:
>> Hi,
>>
>> Actually I don't know how new these are -- certainly newer than the
>> 7.2 release. Is anybody else running the testsuite with
>> native-gdbserver.exp?
>>
>> I'm seeing hundreds of instances of this assert failure:
>>
>> /data/home/msnyder/cvs/localhost/src/gdb/thread.c:619: internal-error:
>> is_thread_state: Assertion `tp' failed.
>
>
> Luckily, this shows up in head but not in the current release branch.
> So it need not hold up the 7.2.1 release.
>
> To see an instance of this, run
>
> make check RUNTESTFLAGS="--target_board=native-gdbserver bang.exp"
>
I have binary-searched it down to a change occurring in the main trunk,
on February 4. One of these:
P bfd/version.h
P gdb/ChangeLog
P gdb/Makefile.in
P gdb/NEWS
P gdb/breakpoint.c
P gdb/breakpoint.h
P gdb/dwarf2read.c
P gdb/mips-linux-tdep.c
P gdb/regcache.c
U gdb/version.in
P gdb/data-directory/Makefile.in
P gdb/doc/ChangeLog
P gdb/doc/gdb.texinfo
P gdb/doc/gdbint.texinfo
cvs update: gdb/python/py-bpevent.c is no longer in the repository
P gdb/python/py-breakpoint.c
cvs update: gdb/python/py-continueevent.c is no longer in the repository
cvs update: gdb/python/py-event.c is no longer in the repository
cvs update: gdb/python/py-event.h is no longer in the repository
cvs update: gdb/python/py-events.h is no longer in the repository
cvs update: gdb/python/py-evtregistry.c is no longer in the repository
cvs update: gdb/python/py-evts.c is no longer in the repository
cvs update: gdb/python/py-exitedevent.c is no longer in the repository
P gdb/python/py-inferior.c
cvs update: gdb/python/py-signalevent.c is no longer in the repository
cvs update: gdb/python/py-stopevent.c is no longer in the repository
cvs update: gdb/python/py-stopevent.h is no longer in the repository
cvs update: gdb/python/py-threadevent.c is no longer in the repository
P gdb/python/python-internal.h
P gdb/python/python.c
cvs update: gdb/syscalls/mips-n32-linux.xml is no longer in the repository
cvs update: gdb/syscalls/mips-n64-linux.xml is no longer in the repository
cvs update: gdb/syscalls/mips-o32-linux.xml is no longer in the repository
P gdb/testsuite/ChangeLog
P gdb/testsuite/gdb.base/catch-syscall.exp
cvs update: gdb/testsuite/gdb.python/py-events.c is no longer in the
repository
cvs update: gdb/testsuite/gdb.python/py-events.exp is no longer in the
repository
cvs update: gdb/testsuite/gdb.python/py-events.py is no longer in the
repository
cvs update: gdb/testsuite/gdb.python/py-evthreads.c is no longer in the
repository
cvs update: gdb/testsuite/gdb.python/py-evthreads.exp is no longer in
the repository
next prev parent reply other threads:[~2011-02-17 2:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 0:55 Michael Snyder
2011-02-17 1:09 ` Michael Snyder
2011-02-17 2:08 ` Michael Snyder [this message]
2011-02-17 18:48 ` Michael Snyder
2011-02-17 20:48 ` Keith Seitz
2011-02-18 16:48 ` [RFA] Fix for " Pierre Muller
2011-02-18 19:30 ` New " Pedro Alves
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=4D5C8312.4030701@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@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