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=-3.3 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no 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 D1BDAC433DF for ; Fri, 16 Oct 2020 12:30:01 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id C4F4F2073A for ; Fri, 16 Oct 2020 12:30:00 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="tYm9pLFb" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C4F4F2073A Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94) (envelope-from ) id 1kTOrW-0002Ku-QE; Fri, 16 Oct 2020 08:29:34 -0400 Received: from mail-qv1-xf2f.google.com ([2607:f8b0:4864:20::f2f]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94) (envelope-from ) id 1kTOrT-0002Kp-3O for Kernelnewbies@kernelnewbies.org; Fri, 16 Oct 2020 08:29:31 -0400 Received: by mail-qv1-xf2f.google.com with SMTP id bl9so980563qvb.10 for ; Fri, 16 Oct 2020 05:29:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DM3357BNy9Rm/hvf6ioLLCCGkLRQej4f2OKQ19KuWzA=; b=tYm9pLFbz3qzNP8omsNhc7eIiGjhaKwu9QLTyIoe+7MsbS/e92B3i58uz4MgQ8+0Hn cMhNAhGs1RO+hvB2FRGVHTUv30W00r7QOsgZ0ZROuVJOra2dzKt6OHpFtOL19zkT/+9B SeLg3Q3D+0tx3x6UgTmsM/krN6eTcZRfxOGzYP08db904F54IH9LBpHCXFtEpsWu9D+Z USEzlCnfM/qbZWwP15B52BYrM9mZJT3Cdd0aSCkZSHhMf+tsGGqiGsePb3gaMUcL8tHR I/13f6/KAEXqmRUmOCFIqWVE70EEfyMf6cJ4xZcAKVpkBaNG2iI00IOZ9pLTCsxi9y5e ObBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DM3357BNy9Rm/hvf6ioLLCCGkLRQej4f2OKQ19KuWzA=; b=NZd761u6kn6QTyRbgUS+HZypIJfwMrIjSo5TRSZ4e29yC66syDnP5wtl7Yi2Z7i9v5 BiWys8dQL3esAcNVCO31uMC2MSAuppViAt77nkDyrbnDqg5yinhH8XjgYjXDytGgShP1 kFAm9VE3o/U1ggAIz9IDyJp4B9HN/L/h8I7CgAt/R3tY3JRU1lOhkr6a27RtcwP8oRgT p/Zpwa1ziK0/KWahEi4HR8uNl5y1ZOSMiAD80f9TxIWhjwVWAi9Xvg7CM9+/mTr0wi6K 8kAK8/IyOVqNDNkFAO5t6j+U9zauP+nO//TtkfMqIW03rlaK3GB9S+yX11MfvHqzEbRF spMA== X-Gm-Message-State: AOAM5320mUkNvquE3Ln3pweE6ifZdOM+ltAU/i+OkSvhReSdgPfychSW jNBQAYeEDd3e3tR9qkw9FfylGJwvlyyQYtQMCWc= X-Google-Smtp-Source: ABdhPJwYZBHQqiDhYLPqMzeKL6TOMSaIQn6YIDlHexWeYnkcLcYHBQ3ibLudjuOkG+FDxyYv2q14M1ojGDhHZ/dMG7Q= X-Received: by 2002:a0c:9d04:: with SMTP id m4mr3663050qvf.50.1602851308898; Fri, 16 Oct 2020 05:28:28 -0700 (PDT) MIME-Version: 1.0 References: <20201015173408.piqrtfpeik2rni36@arch-linux.localdomain> <260903.1602820366@turing-police> <20201016114904.5ffc7ce5ssji7jwy@arch-linux.localdomain> In-Reply-To: <20201016114904.5ffc7ce5ssji7jwy@arch-linux.localdomain> From: Alexander Kapshuk Date: Fri, 16 Oct 2020 15:27:52 +0300 Message-ID: Subject: Re: Oops stack trace missing function addresses To: Adrian Larumbe Cc: =?UTF-8?Q?Valdis_Kl=C4=93tnieks?= , kernelnewbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Fri, Oct 16, 2020 at 2:49 PM Adrian Larumbe wrote: > > > OK, I'll bite. You *are* getting the function name and offset, what additional > > knowledge do you get from knowing the VA? > > I was hoping to use the VA to calculate the C source line where the > fault happens, by substracting the function's VA from the module load > address as revealed by cat /proc/modules, adding the offset within the > function and then passing the offset to addr2line. > > I've just realised I might as well load the module object file into gdb > and do 'info line *(func+offset)'. > > But how would I do this just with addr2line ? scripts/faddr2line path/to/module.ko symbol+0xsym_offset/0xsym_size would give you the C source line referenced by the offset. > > > What architecture is this on? Stack unwinding is architecture-dependent, so > > it may just be the unwinder for that arch doesn't output the virtual address. > > It's a QEMU VM, 'uname -m' claims it's i686. > > > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies