From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) by sourceware.org (Postfix) with ESMTPS id B09673959E6B for ; Wed, 10 Mar 2021 12:14:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B09673959E6B Received: by mail-wr1-x42a.google.com with SMTP id u16so23045512wrt.1 for ; Wed, 10 Mar 2021 04:14:43 -0800 (PST) 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; bh=G1JgdreGjbF1sKMGMVGOVISFv2r3syIKZHgeP+Z+fFQ=; b=uQImElGFcT3Nj15rsq4Glo26yCQWQxhgTbjxTPnPPzEm6pdrnLP1k1BuBTcIJ4BAY7 OsCUNcjpRQP7u3B7XopE0NN68s9QzbhsLOMlpmdsN6YiYb/xw9ltI/nvwUFhWDhTT7My 9g6M8zQ7JIScw7SecTC3QQ7ULz5PAg85obudiTVuCn7AQhdNX/i3I9Ut3qrOsZG1KMLr +skx57yfjBuC3k4cvl1S/Ur+GPnelIQLgYzPqfOwo+1+2uj0tvK0pPxSe8aE/verfbJe mVH+CaFAJtnPNPcON6hF8O0IHRcwB4BOil+RC+MkyH3Usgc45ZOU9BqmOOJnhxcJ+dpF Alaw== X-Gm-Message-State: AOAM530hT2LktRBpX2Kd09cOjmfHE2YKTnYuSg0UN6i2KFNfQnLrpLZq oLhhag8l0f2HXl4Ovx7i1bBvpUmoRdsdCByaaCirlQNILg== X-Google-Smtp-Source: ABdhPJyipi0c+YrDGdnGNQysE7fI1Beqm+6AdbwuAtadowZRe0AR9t4Wet63f0vGq3pHUEnWzl+coYMR1Qiq5xbxik8= X-Received: by 2002:a5d:5906:: with SMTP id v6mr3208843wrd.137.1615378482841; Wed, 10 Mar 2021 04:14:42 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Mahmood Naderan Date: Wed, 10 Mar 2021 13:14:31 +0100 Message-ID: Subject: Re: How to log instructions with GDB To: "Metzger, Markus T" , gdb@sourceware.org X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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: , X-List-Received-Date: Wed, 10 Mar 2021 12:14:46 -0000 I am trying that on virtualbox. I get (gdb) record btrace Target does not support branch tracing. Also, I would like to know where is the file contains "record full" information? Regards, Mahmood On Wed, Mar 10, 2021 at 12:27 PM Metzger, Markus T < markus.t.metzger@intel.com> wrote: > Hello Mahmood, > > There's the 'record' command to start recording the execution. By > default, you'd > get s/w recording ('record full') that also records data. With 'record > btrace' you'd > get a h/w recording solution on systems that support it. > > At least 'record btrace' supports 'record instruction-history', which > should do > what you're looking for. It is supported on recent IA systems. > > There's some documentation on those in the GDB manual. > > Regards, > Markus. > > > -----Original Message----- > > From: Gdb On Behalf Of Mahmood Naderan via > > Gdb > > Sent: Montag, 8. M=C3=A4rz 2021 15:33 > > To: gdb@sourceware.org > > Subject: How to log instructions with GDB > > > > Hi, > > I would like to know if GDB has a mechanism to trace the execution > > instructions while debugging. > > I am looking for a way to write the executed instructions (similar to t= he > > disassembly format) in a file. > > > > Regards, > > Mahmood > Intel Deutschland GmbH > Registered Address: Am Campeon 10, 85579 Neubiberg, Germany > Tel: +49 89 99 8853-0, www.intel.de > Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva > Chairperson of the Supervisory Board: Nicole Lau > Registered Office: Munich > Commercial Register: Amtsgericht Muenchen HRB 186928 >