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 AA5DCC433E7 for ; Thu, 15 Oct 2020 17:34:15 +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 EE8592225F for ; Thu, 15 Oct 2020 17:34:14 +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="I3gK23z1" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EE8592225F 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 1kT78N-0001O3-9Y; Thu, 15 Oct 2020 13:33:47 -0400 Received: from mail-wm1-x342.google.com ([2a00:1450:4864:20::342]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94) (envelope-from ) id 1kT78K-0001Ny-WC for Kernelnewbies@kernelnewbies.org; Thu, 15 Oct 2020 13:33:45 -0400 Received: by mail-wm1-x342.google.com with SMTP id d81so4027744wmc.1 for ; Thu, 15 Oct 2020 10:33:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mime-version:content-disposition; bh=YYk3iiZWSSW5AwWg2A8sfdg1H34rQbKf2R7MqSUy1Xc=; b=I3gK23z1EwYPlaDNQiNhim/NxX2mrkaLKd9gJOc2eoZrWoxgaGdj0wuk2T6xh9HHiA SF3e1b3cR9ZMUVQ8dZcwMVQcwd487lqjRYOW2Xn60gVkbh1mop1235LInDszUvRHbhOB nmECTPln81kc1p1OC2mp/kojoLtaHrR7WsR2vKMfoH5cdUuoA7WokMl6V5yussVQMxUG MnQ0iEG5K+X0kEFQl2vZo675tlTz/iDEMYa8YFw0GzX61eqbdL8OSlwJNf+9MJIZ0CG6 yP8tbHTDLdaLli9vmzLC9kQb8blve/3LBW0e+uANKbsNE+Hy4F4DEKp7iMziuWGTuvju 4EaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition; bh=YYk3iiZWSSW5AwWg2A8sfdg1H34rQbKf2R7MqSUy1Xc=; b=QrS+lNd/aMyKawqnbjUSq9DZwTDilmvJfPftPilGVe0mSFMWJp61yQpzYZBNNA/jTE IqqtG2Ydb9KDuF9lPPdaz/DuzNfx38XXBJLp4zzbsOtuRv/WrDUjVH3XxP6kffx3V81n t+T8Rr7RK+HBu7HI83Gh66psESsGJWF0uPZ06fF8XCsJCO9Jdai3BRQzlCohMPbC14hp VV8IqZaWjhaZDKHt3bTpkpcitoFlFHSV2fQXVIz+vruzujy3gJ6V5z73k/TYYIHvj9+C xTdiK5rG0VywoPKTARGJXq13Cy5e/0L8qvbIHJ+Gqk/k/5SogPIwEB5kHy1uyAlC+kqT cQMQ== X-Gm-Message-State: AOAM532y18wxujQ8Vk4vJZO0lci7Z+9mAVXU/agJ2NsrWYk+v5+8PEUZ dqZaiVSp2sKx4BrnxBBkkD/eD7KHNgu3+Q== X-Google-Smtp-Source: ABdhPJw6BSNU/QFlxFebDfzQVrGm/jourgIQtDoVyTSwV5fOaimkDMMHGlFNPg2d0PI4PqK7hzSqZw== X-Received: by 2002:a1c:7dc5:: with SMTP id y188mr4968291wmc.37.1602783221233; Thu, 15 Oct 2020 10:33:41 -0700 (PDT) Received: from localhost ([2a02:8010:65b5:0:454a:7492:3b3d:a54e]) by smtp.gmail.com with ESMTPSA id t5sm6128366wrb.21.2020.10.15.10.33.40 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 15 Oct 2020 10:33:40 -0700 (PDT) Date: Thu, 15 Oct 2020 18:34:08 +0100 From: Adrian Larumbe To: kernelnewbies Subject: Oops stack trace missing function addresses Message-ID: <20201015173408.piqrtfpeik2rni36@arch-linux.localdomain> MIME-Version: 1.0 Content-Disposition: inline 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: kernelnewbies-bounces@kernelnewbies.org Hi everyone, I wrote a small kernel module where I trigger a page fault by writing to an invalid memory address. This causes an Oops that prints the associated Stack Trace, but contrary to what the kernel documentation claims, I get no VA next to each function in the Call Trace: Call Trace: do_one_initcall+0xfc/0x290 ? cache_alloc_debugcheck_after+0x38/0x270 ? rcu_read_lock_sched_held+0x77/0xa0 ? kmem_cache_alloc_trace+0x2b6/0x330 do_init_module+0x4b/0x1b6 load_module+0x2140/0x24c0 ? find_held_lock+0x2d/0xa0 sys_init_module+0xdd/0x100 do_int80_syscall_32+0x73/0x170 entry_INT80_32+0xcf/0xcf This looks very much unlike what I see in https://www.kernel.org/doc/html/v4.11/admin-guide/bug-hunting.html I was wondering maybe the reason is that I didn't compile the kernel with the right debug options, but a quick glance at the .config file reveals they all seem to be there: CONFIG_DEBUG_INFO=y CONFIG_STACKTRACE=y CONFIG_DEBUG_BUGVERBOSE=y Cheers, Adrian _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies