From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11199 invoked by alias); 9 May 2012 17:46:42 -0000 Received: (qmail 11191 invoked by uid 22791); 9 May 2012 17:46:41 -0000 X-SWARE-Spam-Status: No, hits=-7.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 09 May 2012 17:46:25 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q49HkLCr007521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 May 2012 13:46:21 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q49HkKMp003044; Wed, 9 May 2012 13:46:21 -0400 Message-ID: <4FAAAD6C.1010507@redhat.com> Date: Wed, 09 May 2012 17:46:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Yao Qi CC: gdb-patches@sourceware.org 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> In-Reply-To: <4FA298D4.7010305@codesourcery.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/msg00290.txt.bz2 On 05/03/2012 03:40 PM, Yao Qi wrote: > On 05/03/2012 10:22 PM, Pedro Alves wrote: >> I'm looking at the existing async issues now. We can't just kfail known >> async issues and then propose flipping async on by default. That's cheating. ;-) > > Oh, we should. I tried to fix them, but made no progress after two > days. So I kfail them and post patches first :). Pedro, thanks for > looking at them. Well, it takes me days to understand and fix these issues myself too. ;-) It's just the nature of the beast... 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? I looked at this a couple months ago, but didn't make much progress. I'll try to figure it out next. -- Pedro Alves