From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3404 invoked by alias); 18 May 2012 18:04:51 -0000 Received: (qmail 3388 invoked by uid 22791); 18 May 2012 18:04:50 -0000 X-SWARE-Spam-Status: No, hits=-6.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,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; Fri, 18 May 2012 18:04:37 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4II4aP6009048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 18 May 2012 14:04:37 -0400 Received: from host2.jankratochvil.net (ovpn-116-17.ams2.redhat.com [10.36.116.17]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q4II4XxA015473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 18 May 2012 14:04:36 -0400 Date: Fri, 18 May 2012 18:04:00 -0000 From: Jan Kratochvil To: Pedro Alves Cc: Tom Tromey , gdb-patches@sourceware.org Subject: Re: [downstream patch FYI] workaround stale frame_info * (PR 13866) Message-ID: <20120518180433.GA5305@host2.jankratochvil.net> References: <20120404191416.GA29603@host2.jankratochvil.net> <87obplgz9q.fsf@fleche.redhat.com> <4FB68E47.1080903@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FB68E47.1080903@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) 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/msg00705.txt.bz2 On Fri, 18 May 2012 20:00:39 +0200, Pedro Alves wrote: > It seems to me that combining the both points, we should be able to get back > the old behavior, where calling a breakpoint insertion function wouldn't > invalidate the frame chain. This is not well debuggable compared to the Tom's compile-time verification proposal. There may be workforce to mechanically replace frame_info for frame_id as long as it gets reviewed. Regards, Jan