From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16895 invoked by alias); 18 Aug 2019 08:32:12 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 16885 invoked by uid 89); 18 Aug 2019 08:32:11 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: mail-lj1-f176.google.com Received: from mail-lj1-f176.google.com (HELO mail-lj1-f176.google.com) (209.85.208.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 18 Aug 2019 08:32:10 +0000 Received: by mail-lj1-f176.google.com with SMTP id h15so8797053ljg.10 for ; Sun, 18 Aug 2019 01:32:10 -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=A560SLEX9avZjsKxlPdvsI1tIXP+MnD0VIiFSwsG3dY=; b=DMRpH/IyW9VisRPk0VLpGGOW9XbGRhwBAgJvl3LOn4SkpC7EV6ATN3MB4oYIQtxKYz Yw5OIox4m0QXnUcbAjFH6IVvxqEkQMfTY+IXDQcvp7IK0Q20rY9i3AmbQvdnV6Y+UTvs Y64myZuhVarSTdk06HjHAuBoTtSpzd86+ez2L/dCuhIS4dqBoSTFVaQKuYJbe97Kufbo GdEeC6p5dOYL11/mFsLQgwpDsOKyDobIjtHczZ92s06oDHtV5Zfq8nUNt99VkF4KJE5V zu2X0m3fY3Y7FBah/e7ZHR0A4XrZ3Azq5uGOn2HMpEWUoGe032AtHb/gM/5u6B3O8lPj wBug== MIME-Version: 1.0 References: <20190818041556.GA11323@host1.jankratochvil.net> In-Reply-To: <20190818041556.GA11323@host1.jankratochvil.net> From: William Tambe Date: Sun, 18 Aug 2019 08:32:00 -0000 Message-ID: Subject: Re: gdb command "next" wrongly working as command "step" To: Jan Kratochvil Cc: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-08/txt/msg00022.txt.bz2 On Sat, Aug 17, 2019 at 11:16 PM Jan Kratochvil wrote: > > On Sun, 18 Aug 2019 05:36:34 +0200, William Tambe wrote: > > I having an issue where the gdb command "next" wrongly work as the > > command "step", in that it will step-into functions instead of > > stepping-over functions. > > > > To support single stepping I have implemnted set_gdbarch_software_single_step(). > > > > Is there another function that I need to implement to support > > stepping-over functions ? > > "next" needs properly implemented backtrace/unwinding so that can it can do > "finish" when "next" detects it stepped into a function. Can I have suggestions of locations within the gdb code where I could put breakpoints to trace where the issue I am having is occurring ? Alternatively, what function within the gdb code implement "next" and "finish" ? > > > Jan