From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18370 invoked by alias); 17 Mar 2019 00:23:10 -0000 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 Received: (qmail 18359 invoked by uid 89); 17 Mar 2019 00:23:09 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=H*f:sk:87va0i7, H*i:sk:87va0i7, HX-Languages-Length:778, searching X-HELO: smtp.polymtl.ca Received: from smtp.polymtl.ca (HELO smtp.polymtl.ca) (132.207.4.11) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 17 Mar 2019 00:23:08 +0000 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id x2H0N1MC027702 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sat, 16 Mar 2019 20:23:06 -0400 Received: by simark.ca (Postfix, from userid 112) id B398A1E78F; Sat, 16 Mar 2019 20:23:01 -0400 (EDT) Received: from simark.ca (localhost [127.0.0.1]) by simark.ca (Postfix) with ESMTP id 609841E182; Sat, 16 Mar 2019 20:23:00 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sun, 17 Mar 2019 00:23:00 -0000 From: Simon Marchi To: Andreas Schwab Cc: Justin Paston-Cooper , gdb@sourceware.org Subject: Re: Command to break before exiting stack frame? In-Reply-To: <87va0i74jq.fsf@igel.home> References: <87va0i74jq.fsf@igel.home> Message-ID: <431d242053ca491be67a21d0d95b71a4@polymtl.ca> X-Sender: simon.marchi@polymtl.ca User-Agent: Roundcube Webmail/1.3.6 X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00045.txt.bz2 On 2019-03-16 20:00, Andreas Schwab wrote: > On Mär 16 2019, Justin Paston-Cooper wrote: > >> I can't imagine that I am the first person to suggest or request this. >> Are >> there any architectural or practical reasons as to why this is might >> be >> difficult? > > There may not even be a place where the frame is exited in the current > function due to tail call. Also, inline literal pools or jump tables > can result in false positives when searching for return insns. > > Andreas. I suppose that the list of all function exit points (regardless of whether it is a jump or real return) is an information that the compiler could theoretically produce and encode in the DWARF information? Simon