From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id wv7BNtZsfmB3CQAAWB0awg (envelope-from ) for ; Tue, 20 Apr 2021 01:55:34 -0400 Received: by simark.ca (Postfix, from userid 112) id D131A1F104; Tue, 20 Apr 2021 01:55:34 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 23CD21E01F for ; Tue, 20 Apr 2021 01:55:34 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 4756F3858004; Tue, 20 Apr 2021 05:55:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4756F3858004 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1618898133; bh=zEv8evZbbBli04Wx4gt1j+oFyHwoa5YtDPWQOpteP5Q=; h=Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=moSqCDR50upSLjN3m4xcpF/cwRbnSwCLZC+hcsF2uTJK76iCr66fi2eMI5r8MqDRm sk9Asg7q6eCbdIk1mYCLt5ecd/MCVmpWCUp3j0D56/ghIUGu4SLR/+2RczR5tLOBJG MTnZK9PUdCemh4GLk5sjPi0SDTtV4PwB1naoSxNY= Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) by sourceware.org (Postfix) with ESMTPS id 3C6B23858004 for ; Tue, 20 Apr 2021 05:55:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3C6B23858004 Received: by mail-pj1-x102e.google.com with SMTP id nk8so6081200pjb.3 for ; Mon, 19 Apr 2021 22:55:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=CYL1f00ZPMVOYp4E68QzRAPqRjrXwWZuW+XQ+1FKeQ0=; b=Qtc4BPG/ISXdBwB4wA0DwbnqxqD+Ey1eAlhwtvl2OOeWAMhgitF8DwbVprFPIv1vgX +qUtCYDbyypk5zgvB1VD3qFVi+EYqv0Hx0s9FLauJOjqpmy/mp7JHFtrmu9mZ7myexcb JSt/x+VQL+1eYwE9jBIfMiUJqzm40YVU0rrg2ZM+M1kDpjUEkvJAXKB1ht7EXg7G5E3g ObbmPBgO/ZRYmAvEOalSSZwhDOCN0n4suRs0EDadpnlc1y/K4Rauy2WZPTK5aleegtXU puQg4IblPVkObhKy66r4dl4Fo5OX4qjdVlBzN+qU1mUINnNvWTptDd60B/al/+Pp/aie C9cw== X-Gm-Message-State: AOAM531grmwdqx67yPfkZd6ZoXcDs18/J0e5F/QZCSqAAyUi1MSry9dx Fanh7/r5cH6QwpGm8vmHP7zI32jW5WSaFxzNHJhbj27KQ3jiWA== X-Google-Smtp-Source: ABdhPJxIxERhPDBVtJuyUjjMIL3mTH6zwf9RBtiemTmUBky2OAMy7saXm3D3p+ufgKBpY5RVepCOdkIjLfqWGfzz6Hg= X-Received: by 2002:a17:902:4c:b029:ec:9f61:6c4d with SMTP id 70-20020a170902004cb02900ec9f616c4dmr10922354pla.22.1618898129843; Mon, 19 Apr 2021 22:55:29 -0700 (PDT) MIME-Version: 1.0 Date: Tue, 20 Apr 2021 11:25:18 +0530 Message-ID: Subject: GDB Stacktrace for optimized code! To: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: , From: Thamil K via Gdb Reply-To: Thamil K Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" Hi Geeks, For programs compiled with -O2, where the compiler uses 'jmp' where possible instead of 'call' or where callee doesn't push $rbp onto the stack, gdb is still able to generate stack trace properly. But by inspecting the $rbp and return address, I am unable to trace back the calls. I would like to know how gdb synthesises the stack trace ? Any pointers on documentation? Thanks in advance. Thanks Thamil