public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "toma.bilius at enea dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/16729] New: wrong tracepoint bytedcode doumentation for rot
Date: Thu, 20 Mar 2014 13:38:00 -0000	[thread overview]
Message-ID: <bug-16729-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 16729
           Summary: wrong tracepoint bytedcode doumentation for rot
           Product: gdb
           Version: 7.7
            Status: NEW
          Severity: normal
          Priority: P2
         Component: breakpoints
          Assignee: unassigned at sourceware dot org
          Reporter: toma.bilius at enea dot com

The description for rot function from
https://sourceware.org/gdb/onlinedocs/gdb/Bytecode-Descriptions.html specifies
that rot should do the rotation a b c -> c b a. However, in the implementation
(gdb_eval_agent_expr) the rotation is a b c -> c a b

Here is the code that does this:

          case gdb_agent_op_rot:
      {
        ULONGEST tem = stack[sp - 1];

        stack[sp - 1] = stack[sp - 2];
        stack[sp - 2] = top;
        top = tem;
      }
      break;

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


             reply	other threads:[~2014-03-20 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 13:38 toma.bilius at enea dot com [this message]
2014-03-20 13:39 ` [Bug breakpoints/16729] " toma.bilius at enea dot com
2024-01-08 17:38 ` ssbssa at sourceware dot org

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-16729-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).