From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) by sourceware.org (Postfix) with ESMTPS id 329093858D28 for ; Tue, 14 Dec 2021 10:22:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 329093858D28 Received: by mail-pl1-x629.google.com with SMTP id k4so13217852plx.8 for ; Tue, 14 Dec 2021 02:22:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bKtKPnMu3utuo3sMhQUSarrsD6mF00gElprgtaqjbUI=; b=GE4T7ByGE4hxJRt69y4ReX1w2wWsuxS59EexdNxpP+zOzEpixIudgS/EtX3R4DbrYC DwYEF3cEeSTsRzTfw1XOmibDPuigL5M3GZ/PFIU0ezt4L+0ZDLKeX7A8GoHon1sBU5yX v1Xx3EIDfNmKmvCP9Cs04bUxK7n8CYsCyeTJoHpkQUifGSpsjJNE21IhY388SVy3K9NM mTESx73DBLKtgxUcQ0FtXPaFB3Cf9BtWhU847WmUrvmKEFvNSUIohkWVXsK05ELp1S9u dXU49AZ2p/uOPOJxo0ud0w6k8yZ513VKQ/P0Cvm8I2oK/aJ3wd6na0VTkEz4D3ludNxW lYLg== X-Gm-Message-State: AOAM532U+g0J31Ikc2nCZUpAE2gO6uEDnWNUO8RdolgoC9NX2lTXRDLp yeQxmlq0v/0gKNLT2MO6Z+11zICIEzk4frliHSQEViROUVE= X-Google-Smtp-Source: ABdhPJxqMkkAuyvzOonkBa1q9hiAn4aDVaNe08mS6y+SRxyGDwNFNCr8ObfysVmJDvSzzWM9GsBs0l9qcIWcrj1lTiI= X-Received: by 2002:a17:90a:384d:: with SMTP id l13mr4785856pjf.104.1639477344142; Tue, 14 Dec 2021 02:22:24 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Vimal Agrawal Date: Tue, 14 Dec 2021 15:52:13 +0530 Message-ID: Subject: Not able to decode local/ stack variables in vmcore To: gdb@sourceware.org Cc: Vimal Agrawal Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2021 10:22:26 -0000 I don't see any option to see local variables in vmcore using crash utility. Tried gdb as well. Gdb is not able to dump stack. (gdb) bt #0 sysrq_handle_crash (key=99) at drivers/tty/sysrq.c:147 Backtrace stopped: Cannot access memory at address 0xffffb8c6c132fe40 (gdb) x 0xffffb8c6c132fe40 0xffffb8c6c132fe40: Cannot access memory at address 0xffffb8c6c132fe40 (gdb) info reg rsp rsp 0xffffb8c6c132fe38 0xffffb8c6c132fe38 (gdb) I have loaded symbols on specific .text, .data and .bss load addresses using following commands: > gdb -c kcrash_vmcore gdb> add-symbol-file ~/crash3/vmlinux 0xffffffff97000000 -s .data 0xffffffff97c00000 -s .bss 0xffffffff97fa5000 I could decode .text and global .data symbols but not stack addresses and local variables. I have tried enabling CONFIG_FRAME_POINTER and also tried the latest version of gdb and crash as well but no help. Can someone please suggest and comment if this is indeed possible with gdb/crash to decode local variables from vmcore? Vimal Agrawal