From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7574 invoked by alias); 17 Feb 2011 18:48:48 -0000 Received: (qmail 7566 invoked by uid 22791); 17 Feb 2011 18:48:47 -0000 X-SWARE-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 17 Feb 2011 18:48:37 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 4BCCC13403; Thu, 17 Feb 2011 10:48:36 -0800 (PST) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost4.vmware.com (Postfix) with ESMTP id 3E79DC9F99; Thu, 17 Feb 2011 10:48:36 -0800 (PST) Message-ID: <4D5D6D83.8030302@vmware.com> Date: Thu, 17 Feb 2011 18:48:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.24 (X11/20101201) MIME-Version: 1.0 To: "gdb@sourceware.org" , swagiaal@redhat.com, oguzkayral@gmail.com Subject: Re: New testsuite errors with gdbserver (remote) References: <4D5C71F6.80208@vmware.com> <4D5C7552.4010708@vmware.com> <4D5C8312.4030701@vmware.com> In-Reply-To: <4D5C8312.4030701@vmware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00098.txt.bz2 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 Oguz Kayral * 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.