From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27060 invoked by alias); 10 May 2012 12:09:09 -0000 Received: (qmail 27045 invoked by uid 22791); 10 May 2012 12:09:07 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 10 May 2012 12:08:53 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1SSSAu-0004kc-QL from Yao_Qi@mentor.com ; Thu, 10 May 2012 05:08:52 -0700 Received: from SVR-ORW-FEM-03.mgc.mentorg.com ([147.34.97.39]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 10 May 2012 05:08:52 -0700 Received: from [127.0.0.1] (147.34.91.1) by svr-orw-fem-03.mgc.mentorg.com (147.34.97.39) with Microsoft SMTP Server id 14.1.289.1; Thu, 10 May 2012 05:08:51 -0700 Message-ID: <4FABAFB3.2000503@codesourcery.com> Date: Thu, 10 May 2012 12:09:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Pedro Alves CC: Subject: Re: [PATCH v4 0/14] Run all-stop on non-stop target References: <1336050869-29605-1-git-send-email-yao@codesourcery.com> <4FA294B7.1040506@redhat.com> <4FA298D4.7010305@codesourcery.com> <4FAAAD6C.1010507@redhat.com> In-Reply-To: <4FAAAD6C.1010507@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-05/txt/msg00333.txt.bz2 On 05/10/2012 01:46 AM, Pedro Alves wrote: > I see this in sync vs async: > > PASS: gdb.python/py-finish-breakpoint.exp: set FinishBreakpoint with default frame value > PASS: gdb.python/py-finish-breakpoint.exp: set FinishBreakpoint > PASS: gdb.python/py-finish-breakpoint.exp: check return_value at init > -PASS: gdb.python/py-finish-breakpoint.exp: check MyFinishBreakpoint hit > -PASS: gdb.python/py-finish-breakpoint.exp: check return_value > -PASS: gdb.python/py-finish-breakpoint.exp: check finishBP on default frame has been hit > -PASS: gdb.python/py-finish-breakpoint.exp: ensure that finish bp is invalid afer normal hit > -PASS: gdb.python/py-finish-breakpoint.exp: return to main() > -PASS: gdb.python/py-finish-breakpoint.exp: check FinishBP not allowed in main > +FAIL: gdb.python/py-finish-breakpoint.exp: check MyFinishBreakpoint hit (GDB internal error) > +ERROR: Could not resync from internal error (timeout) > +UNRESOLVED: gdb.python/py-finish-breakpoint.exp: check return_value (timeout) > +ERROR: Process no longer exists > +UNRESOLVED: gdb.python/py-finish-breakpoint.exp: check finishBP on default frame has been hit > +ERROR: Couldn't send python print finishbp.is_valid() to GDB. > +UNRESOLVED: gdb.python/py-finish-breakpoint.exp: ensure that finish bp is invalid afer normal hit > +ERROR: Couldn't send finish to GDB. > +UNRESOLVED: gdb.python/py-finish-breakpoint.exp: return to main() > +ERROR: Couldn't send python MyFinishBreakpoint (None, gdb.selected_frame ()) to GDB. > +UNRESOLVED: gdb.python/py-finish-breakpoint.exp: check FinishBP not allowed in main > > Do you see it too? > Yes, I saw them as well on both native gdb and remote. This is the last set problems of on async. > I looked at this a couple months ago, but didn't make much progress. I'll try to > figure it out next. Thanks for looking at these issues, Pedro. -- Yao (齐尧)