Received: by 10.223.176.5 with SMTP id f5csp1291805wra; Fri, 2 Feb 2018 14:51:46 -0800 (PST) X-Google-Smtp-Source: AH8x225NrioI6bhQj/W6WI0OU9+/kfguUdbbB6hIftMNJJBlEu7JrvHgllW4WkLKasRMr8ctJ0a8 X-Received: by 10.99.150.2 with SMTP id c2mr6300352pge.424.1517611905965; Fri, 02 Feb 2018 14:51:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517611905; cv=none; d=google.com; s=arc-20160816; b=Fo5iaEe8ukyzudwvg6BkXaFSLZ0Xf5okFJq/UEQ6Gx1lDT+/CJXQGZ3ZLTffE2hOrQ jtGI9vzUHaN7ed/Aed6WOQ17RcurUNSFbLbUhciCI5oBAbWji1Rz6b+hxdYU4m8ebOYb ZOZapn6klm5DtYlhylnOwK3V+7vB3sd/lIt08N8vm0LUVO8npqHkhfN8GzFwQ3vuMLxU BQ7vy23jXX8/ZO8PMXEnedDwAYuNKX3xmlvyRv6nORxC8+Dtsv1ZQpIZmEm721S7Zx3D +qF6f9hkaP99T6WmAcgstG8g+0L4G0cZF96Sk71Z8n9hy6HKdv+2TdIGjR6XLUZhI9hi iTnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=zkJHIWefY4CgbBzRqsmjzGrvXUFCL0bHmZWxN/6vRa4=; b=WXaJeD7YH+PcZs1loJDQgknzyAjPcDaKrLE/D2UerScPzQn7OINqElhoKtGavfqJ58 8n+B/ws1pJuUY1EtkPKzbiAYZrdJj91JsmRoaKJplbxWuAVCpSBbVpTnPM4E7izi1X9S nZJtGumUN/liJ2PI5Nrz3Fjt4lbsUgDQ8X2kwrIO08hAVNvvNa0NTCjC0MvL3D3XtQtT ipOokSB/s7tSWhRia0qeZ8jrlV1lBy8snfxi20PQ5VnXvig69M9ICK0qJbiO1tT7qvlh IuZPO1n2HpMkWJ17c+BHAaPOdH2l1D12dXIyzLGKfyzNLx4seSbpifFnbS/iRT32t85S xajQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o22si2540840pfi.277.2018.02.02.14.51.31; Fri, 02 Feb 2018 14:51:45 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753003AbeBBWWl (ORCPT + 99 others); Fri, 2 Feb 2018 17:22:41 -0500 Received: from mga06.intel.com ([134.134.136.31]:25343 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752215AbeBBWWd (ORCPT ); Fri, 2 Feb 2018 17:22:33 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Feb 2018 14:22:32 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,451,1511856000"; d="scan'208";a="24494127" Received: from agluck-desk.sc.intel.com (HELO agluck-desk) ([10.3.52.160]) by FMSMGA003.fm.intel.com with ESMTP; 02 Feb 2018 14:22:32 -0800 Date: Fri, 2 Feb 2018 14:22:32 -0800 From: "Luck, Tony" To: Sergei Trofimovich Cc: Fenghua Yu , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ia64: fix ptrace(PTRACE_GETREGS) (unbreaks strace, gdb) Message-ID: <20180202222231.23favlxecnxcencr@agluck-desk> References: <20180202221224.16597-1-slyfox@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180202221224.16597-1-slyfox@gentoo.org> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 02, 2018 at 10:12:24PM +0000, Sergei Trofimovich wrote: > The strace breakage looks like that: > ./strace: get_regs: get_regs_error: Input/output error > > It happens because ia64 needs to load unwind tables > to read certain registers. Unwind tables fail to load > due to GCC quirk on the following code: > > extern char __end_unwind[]; > const struct unw_table_entry *end = (struct unw_table_entry *)table_end; > table->end = segment_base + end[-1].end_offset; > > GCC does not generate correct code for this single memory > reference after constant propagation (see https://gcc.gnu.org/PR84184). I'm not seeing this ... probably because I build with a pre-historic 4.3.4 version of gcc. Do you know which version(s) are affected? I'm not looking for an exhaustive list, just the one on which you found this would be good. -Tony