From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23575 invoked by alias); 17 Dec 2013 12:39:49 -0000 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 Received: (qmail 23561 invoked by uid 89); 17 Dec 2013 12:39:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=AWL,BAYES_00,GARBLED_BODY autolearn=no version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 17 Dec 2013 12:39:47 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1Vstw7-0007EK-SG from Yao_Qi@mentor.com ; Tue, 17 Dec 2013 04:39:43 -0800 Received: from SVR-ORW-FEM-04.mgc.mentorg.com ([147.34.97.41]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 17 Dec 2013 04:39:43 -0800 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-04.mgc.mentorg.com (147.34.97.41) with Microsoft SMTP Server id 14.2.247.3; Tue, 17 Dec 2013 04:39:38 -0800 Message-ID: <52B0457A.6040804@codesourcery.com> Date: Tue, 17 Dec 2013 12:39:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Pedro Alves CC: Subject: Re: [PATCH] "tfind" across unavailable-stack frames. References: <1366214779.30939.1@abidh-ubunto1104> <516F11B9.8030202@redhat.com> <52AB48B6.6040206@redhat.com> <52ABF8D7.1050805@codesourcery.com> <52AF27F7.2060500@redhat.com> <52B01328.8030707@codesourcery.com> <52B022C8.3090504@redhat.com> In-Reply-To: <52B022C8.3090504@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2013-12/txt/msg00639.txt.bz2 On 12/17/2013 06:09 PM, Pedro Alves wrote: > It is clear, but it is not as precise or sufficient. A wild > card means that given these frame ids: > > fid1: {code_p,stack_p,special_p} > fid2: {!code_p,stack_p,!special_p} > > fid3: {code_p,stack_p,special_p} > fid4: {code_p,stack_p,!special_p} > > {fid1, fid2} with same stack addresses, > and {fid3, fid4} with same code and stack addresses, > both: > > frame_id_eq(fid1, fid2) > frame_id_eq(fid3, fid4) > > return true. > >> > I don't see >> > any extra information the last sentence "Otherwise, xxxxx" delivered >> > except confusion. > The extra information indicates that e.g., frame_id_eq(fid3, fid4) > above returns true, not false, as one might at first expect. Thanks for giving these examples. > > Whether this whole wildcarding business is a good idea, is > another story. Anyway, I've got use to it now. :) -- Yao (齐尧)