public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "czgf2v at 163 dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30246] New: gdb record and replay , sometime variable operate wrong. but rr works, based on ryzen 4800h cpu(zen architecture)
Date: Sun, 19 Mar 2023 17:08:26 +0000	[thread overview]
Message-ID: <bug-30246-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30246

            Bug ID: 30246
           Summary: gdb record and replay , sometime variable operate
                    wrong. but rr works, based on ryzen 4800h cpu(zen
                    architecture)
           Product: gdb
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: czgf2v at 163 dot com
  Target Milestone: 14.1

run 
---------------------
$make -f Makefile;gdb ./main -ex "source ./debug.gdb"
---------------------

after a while,(this bug happens after doing many operations with random numbers
and ‘rc’ command)

output on my machine (the output is wrong)
-------------
...
Active record target: record-full
Replay mode:
Lowest recorded instruction number is 1.
Current instruction number is 257733.
Highest recorded instruction number is 257773.
Log contains 257773 instructions.
Max logged instructions is 2000000000.
$1 = 10100110110111001001101
$2 = 101001101101110010011010
$3 = 0
-------------

but with rr
-------------
$ rr ./main
$ rr replay /home/czg/.local/share/rr/main-3
...
source ./debug_rr.gdb
-------------
(because in rr use 'next' to run and no ‘record’ command needed [rr has
recorded all before], so gdb command file slightly differ)


output on my machine (the output is right)
-------------
$1 = 111111010111001001000010
$2 = 111111010111001001000010
$3 = 1
-------------

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-03-19 17:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 17:08 czgf2v at 163 dot com [this message]
2023-03-19 17:09 ` [Bug gdb/30246] " czgf2v at 163 dot com
2023-03-19 17:09 ` czgf2v at 163 dot com
2023-03-19 17:10 ` czgf2v at 163 dot com
2023-03-19 17:13 ` czgf2v at 163 dot com
2023-03-19 17:15 ` czgf2v at 163 dot com
2023-03-19 17:20 ` czgf2v at 163 dot com
2023-03-19 17:22 ` czgf2v at 163 dot com
2023-03-19 17:24 ` czgf2v at 163 dot com
2023-03-19 17:25 ` czgf2v at 163 dot com
2023-03-19 17:26 ` czgf2v at 163 dot com
2023-03-19 17:28 ` czgf2v at 163 dot com
2023-03-19 17:45 ` czgf2v at 163 dot com
2023-03-20  0:51 ` [Bug gdb/30246] gdb record full, br … and rc. Sometime " czgf2v at 163 dot com
2023-03-20 15:33 ` czgf2v at 163 dot com
2023-03-21  4:18 ` sam at gentoo dot org
2023-03-21 15:01 ` [Bug record/30246] " tromey at sourceware dot org
2023-07-05 14:21 ` brobecker at gnat dot com
2023-07-30 22:51 ` brobecker at gnat dot com
2023-07-30 22:53 ` brobecker at gnat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30246-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).