Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp143379imm; Tue, 9 Oct 2018 15:21:19 -0700 (PDT) X-Google-Smtp-Source: ACcGV60al+4uLx+f0wSIARc+vXpequOdvHXbWF0kEvtx+8O3FMrLye1MA0/+5NiZuWBPq1pD6X/5 X-Received: by 2002:a63:c746:: with SMTP id v6-v6mr27816176pgg.108.1539123679395; Tue, 09 Oct 2018 15:21:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539123679; cv=none; d=google.com; s=arc-20160816; b=wiuc2GceIGhpQfDOJKVmUqe+MWq0APS5Mn4SafF3BcmHyNUCyuyhyEkenCOf4MKHHR euPmWeWM5ucUUnPzbjqycwLq3yWQkjy97MzwVe/qY8aJBgQ6CpWR9Ef86E2i/IQQHiMB kQ3AS/e5EjNjhqF4TDNcAG8FNCzwW3FAL02FtwTQoFZKzkauyViHzH6unqN2CWg8zDD7 MD6rWZS6+tMEi+oF2A6j19siyCuD3dY0yLd1Rmc385XTD8K/TgVH0wIvTq4+QD+/Yd5U uS+yEJp9zMJYI4Ta3Q1zEKI3sDq+7KOT8Djuac2oWhQ8dviKkVn8049Khvk98fUa/pKy rjKA== 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; bh=KQY3+qtZaID9cK2btb+WhuxnFT+qDnOnszV8Tk2O0zM=; b=wbVFL+ffMNcq1dtbOt1bGslSi63vxR+EPmkLuWcpK8Q8OWNYq5NOLHnKyhiK9p2sMc FTRP2ctKTmmSF73BiGT1/+BrRdd4FJHA8u/OSof840KFIKZuzmdU+tqlqRUDr2sibgEF 4j5wzfqn7mSVd75bgvx+AxQBAxjzCl0d/KalUQfEsWO+2Z7TXodn/VXo6Sr3OMWVGgyv 2EJGvDC4JxCVQPRw9cYo7IwFiLXYgI55Xqc9Ic2dkVJaHpoxg1WR8DoIPRvzF5Dx69ym EDOxFfWzICdsBEMoYftUwkEI+gD0zEFC3MvCuM+nxQ2W1OQrYScIIFUKOmPVbtSz3xZV Ukww== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p7-v6si22003142plo.159.2018.10.09.15.21.04; Tue, 09 Oct 2018 15:21:19 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728003AbeJJFjM (ORCPT + 99 others); Wed, 10 Oct 2018 01:39:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:53678 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727972AbeJJFjM (ORCPT ); Wed, 10 Oct 2018 01:39:12 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6C4EE7F6A0; Tue, 9 Oct 2018 22:20:07 +0000 (UTC) Received: from krava (ovpn-204-35.brq.redhat.com [10.40.204.35]) by smtp.corp.redhat.com (Postfix) with SMTP id 1EFD77C82C; Tue, 9 Oct 2018 22:20:04 +0000 (UTC) Date: Wed, 10 Oct 2018 00:20:04 +0200 From: Jiri Olsa To: Anthony LaTorre , andipan Das Cc: peterz@infradead.org, mingo@redhat.com, jolsa@kernel.org, acme@kernel.org, alexander.shishkin@linux.intel.com, namhyung@kernel.org, linux-kernel@vger.kernel.org Subject: Re: perf report segfault Message-ID: <20181009222004.GA19295@krava> References: <20181009164743.GA22886@krava> <20181009214158.GB31206@krava> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Tue, 09 Oct 2018 22:20:07 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 09, 2018 at 04:47:31PM -0500, Anthony LaTorre wrote: > I can try building perf from the latest sources. I've attached the > perf.data and perf.data.tar.bz2 from the test program I sent earlier. cool, reproduced.. it seems to get introduced by: 2a9d5050dc84 perf script: Show correct offsets for DWARF-based unwinding reverting that patch fixes the issue for me, but looks like we could just make th attached check and prevent the crash adding Sandipan Das to the loop, the author of that commit, any idea? thanks, jirka --- diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c index c4acd2001db0..ea68c805c7ac 100644 --- a/tools/perf/util/machine.c +++ b/tools/perf/util/machine.c @@ -2312,7 +2312,6 @@ static int unwind_entry(struct unwind_entry *entry, void *arg) { struct callchain_cursor *cursor = arg; const char *srcline = NULL; - u64 addr; if (symbol_conf.hide_unresolved && entry->sym == NULL) return 0; @@ -2320,13 +2319,15 @@ static int unwind_entry(struct unwind_entry *entry, void *arg) if (append_inlines(cursor, entry->map, entry->sym, entry->ip) == 0) return 0; - /* - * Convert entry->ip from a virtual address to an offset in - * its corresponding binary. - */ - addr = map__map_ip(entry->map, entry->ip); + if (entry->map) { + /* + * Convert entry->ip from a virtual address to an offset in + * its corresponding binary. + */ + u64 addr = map__map_ip(entry->map, entry->ip); + srcline = callchain_srcline(entry->map, entry->sym, addr); + } - srcline = callchain_srcline(entry->map, entry->sym, addr); return callchain_cursor_append(cursor, entry->ip, entry->map, entry->sym, false, NULL, 0, 0, 0, srcline);