From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7B827C43331 for ; Thu, 26 Mar 2020 09:59:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 45BC02070A for ; Thu, 26 Mar 2020 09:59:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="YZIMpPxY" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726590AbgCZJ7r (ORCPT ); Thu, 26 Mar 2020 05:59:47 -0400 Received: from us-smtp-delivery-74.mimecast.com ([63.128.21.74]:56963 "EHLO us-smtp-delivery-74.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726354AbgCZJ7q (ORCPT ); Thu, 26 Mar 2020 05:59:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1585216785; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1TjD8tde64nLcXz59JAqotEi1gdMOPkONC4hzcCw/WY=; b=YZIMpPxYLoOQFKSvcdNYICm7jBzu+ueLYw1fsXnTNJI+z167KXKbkj1IL+4MGgs7h5Ox5E h0HX8/OelnNuTfffUQ1Uk0pCa+BJeQO6z2u8+Y6vMG82DebV1PWutAUCTiNPQihDVa6voY XFRhAoGZASy5oM6b81zsz25ZgLtpb3Y= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-180-WTIc1PDbNRO4xae_hNxIzg-1; Thu, 26 Mar 2020 05:59:37 -0400 X-MC-Unique: WTIc1PDbNRO4xae_hNxIzg-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 45CE48010FC; Thu, 26 Mar 2020 09:59:34 +0000 (UTC) Received: from krava (unknown [10.40.192.119]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 945105D9CD; Thu, 26 Mar 2020 09:59:31 +0000 (UTC) Date: Thu, 26 Mar 2020 10:59:28 +0100 From: Jiri Olsa To: ahmadkhorrami Cc: Steven Rostedt , Arnaldo Carvalho de Melo , Linux-trace Users , Peter Zijlstra , linux-trace-users-owner@vger.kernel.org, Jin Yao , Milian Wolff , Namhyung Kim , Changbin Du , Andi Kleen Subject: Re: Wrong Perf Backtraces Message-ID: <20200326095928.GF1947699@krava> References: <9551c616b045299482fc9e26281c1062@ut.ac.ir> <20200325192858.GC19495@redhat.com> <4ffb7e2b6e272c20616fbf133a125fdf@ut.ac.ir> <20200325203921.GB1947699@krava> <20200325210252.GC1947699@krava> <20200325170932.34d52269@gandalf.local.home> <20200325214624.GD1947699@krava> <52904543671bcb68ea9109b90c3e4267@ut.ac.ir> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52904543671bcb68ea9109b90c3e4267@ut.ac.ir> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Sender: linux-trace-users-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-trace-users@vger.kernel.org On Thu, Mar 26, 2020 at 03:39:31AM +0430, ahmadkhorrami wrote: > An here is the second one: > https://gofile.io/?c=oGxgSM thanks, so far I don't see that, but I think it's because the 'inline' code does not resolve the libc dso correctly, CC-ing few other folks.. so I'm able to get: EvJobScheduler 17382 13006.872877: 10000 mem_load_uops_retired.l3_miss:uppp: 7fffd2e06588 5080022 N/A|SNP N/A|TLB N/A|LCK N/A 7ffff4b04c74 [unknown] (/lib/x86_64-linux-gnu/libc-2.27.so) 7ffff4b072ec malloc+0x27c (/lib/x86_64-linux-gnu/libc-2.27.so) 7fffd9872ddd gmalloc+0xd (/usr/lib/x86_64-linux-gnu/libpoppler.so.73.0.0) 7fffd9873391 copyString+0x11 (/usr/lib/x86_64-linux-gnu/libpoppler.so.73.0.0) while you see: EvJobScheduler 17382 13006.872877: 10000 mem_load_uops_retired.l3_miss:uppp: 7fffd2e06588 5080022 N/A|SNP N/A|TLB N/A|LCK N/A 7ffff4b04c74 _int_malloc+0x9a4 (/lib/x86_64-linux-gnu/libc-2.27.so) 7ffff4b072ec __GI___libc_malloc+0x27c (inlined) 7fffd9872ddd gmalloc+0xd (/usr/lib/x86_64-linux-gnu/libpoppler.so.73.0.0) 7fffd9872ddd gmalloc+0xd (/usr/lib/x86_64-linux-gnu/libpoppler.so.73.0.0) so for some reason I don't resolve 7ffff4b04c74, which might be the reason I don't see the following address twice as you do: 7fffd9872ddd gmalloc+0xd (/usr/lib/x86_64-linux-gnu/libpoppler.so.73.0.0) 7fffd9872ddd gmalloc+0xd (/usr/lib/x86_64-linux-gnu/libpoppler.so.73.0.0) the previous field (7ffff4b072ec) is resolved by the 'inline' code, so I wonder it's related I needed to make some changes to utils/srcline.c to be able to properly open dso via buildid cache, I pushed it to: git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git perf/callchain here are the steps to get above output: download perf.data and perf archive data from: https://gofile.io/?c=o95O7N http://gofile.io/?c=qk6oXv $ unxz ./perf.data.xz $ tar xvf perf.data.tar.bz2 -C ~/.debug compile perf from aobve tree/branch and run: $ perf script -i perf.data I think we might be missing some libraries in 'perf archive' by not following debug_link section, will check on this jirka > Regards > On 2020-03-26 02:51, ahmadkhorrami wrote: > > > Here is the link for the gmallocn()s: > > http://gofile.io/?c=qk6oXv > > I will send the second one as soon as the upload is finished: > > > > Regards. > > > > On 2020-03-26 02:16, Jiri Olsa wrote: > > > > On Thu, Mar 26, 2020 at 02:07:39AM +0430, ahmadkhorrami wrote: > > > > Here is the link for the gmallocn() case: > > https://gofile.io/?c=o95O7N > > The output for the second case is big. I have a small one produced > > several > > days ago the link of which is as follows: > > https://gofile.io/?c=OIPCjx > > looking good, but I still need you t run 'perf archive' on top of your > > data and send me the perf.data.tar.bz2 it generates, like: > > > > [jolsa@krava perf]$ sudo ./perf record > > ^C[ perf record: Woken up 1 times to write data ] > > [ perf record: Captured and wrote 1.675 MB perf.data (6248 samples) ] > > > > [jolsa@krava perf]$ sudo ./perf archive > > Now please run: > > > > $ tar xvf perf.data.tar.bz2 -C ~/.debug > > > > wherever you need to run 'perf report' on. > > > > I need that perf.data.tar.bz2 generated from your data > > > > thanks, > > jirka > > > > Regards. > > > > On 2020-03-26 01:39, Steven Rostedt wrote: > > > > On Wed, 25 Mar 2020 22:02:52 +0100 > > Jiri Olsa wrote: > > > > yea, no luck.. so if you could generate some reasonable small > > perf.data that > > shows the issue and send it over together with 'perf archive' data > > privately > > to me and to whoever else ask for it, so we don't polute the list.. > > Right. And it may be better if you compress it too. > > > > xz perf.data > > > > and attach the perf.data.xz (and only privately send it to Mr. Olsa). > > > > -- Steve > > > > or if you could put it somewhere on the web/ftp.. that'd be best >