From: Michael Snyder <msnyder@vmware.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>,
swagiaal@redhat.com, oguzkayral@gmail.com
Subject: Re: New testsuite errors with gdbserver (remote)
Date: Thu, 17 Feb 2011 18:48:00 -0000 [thread overview]
Message-ID: <4D5D6D83.8030302@vmware.com> (raw)
In-Reply-To: <4D5C8312.4030701@vmware.com>
Michael Snyder wrote:
> 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:
Somewhat to my surprise, these new failures narrow down to this change:
2011-02-04 Sami Wagiaalla <swagiaal@redhat.com>
Oguz Kayral <oguzkayral@gmail.com>
* python/py-inferior.c (python_on_normal_stop): New function.
(python_on_resume): New function.
(python_inferior_exit): New function.
(gdbpy_initialize_inferior): Add normal_stop, target_resumed, and
inferior_exit observers.
* python/py-evtregistry.c: New file.
* python/py-threadevent.c : New file.
* python/py-event.c: New file.
* python/py-evts.c: New file.
* python/py-continueevent.c: New file.
* python/py-bpevent.c: New file.
* python/py-signalevent.c: New file.
* python/py-exetiedevent.c: New file.
* python/py-breakpoint.c (gdbpy_breakpoint_from_bpstats): New
function.
Move struct breakpoint_object from here...
* python/python-internal.h: ... to here.
* python/py-event.h: New file.
* python/py-events.h: New file.
* Makefile.in (SUBDIR_PYTHON_OBS): Add py-breakpointstopevent.o,
py-continueevent.o, py-event.o, py-eventregistry.o, py-events.o,
py-exitedevent.o, py-signalstopevent.o, and py-stopevent.o.
(SUBDIR_PYTHON_SRCS): Add py-breakpointstopevent.c,
py-continueevent.c, py-event.c, py-eventregistry.c, py-events.c,
py-exitedevent.c, py-signalstopevent.c, and py-stopevent.c.
Add build rules for all the above.
next prev parent reply other threads:[~2011-02-17 18:48 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
2011-02-17 18:48 ` Michael Snyder [this message]
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=4D5D6D83.8030302@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=oguzkayral@gmail.com \
--cc=swagiaal@redhat.com \
/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