public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "xdje42 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/12444] disassemble /m errors on inlined code?
Date: Sat, 15 Aug 2015 04:53:00 -0000	[thread overview]
Message-ID: <bug-12444-4717-NvV4N4DMOx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12444-4717@http.sourceware.org/bugzilla/>

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

Doug Evans <xdje42 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |xdje42 at gmail dot com
         Resolution|---                         |FIXED

--- Comment #4 from Doug Evans <xdje42 at gmail dot com> ---
I tested this with trunk, and didn't see the bug, so I'm guessing it's fixed
now.
I don't know which patch fixed it.

[Which isn't to say /m is useful with inlined code,
just that "make test" worked for me.]

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


      parent reply	other threads:[~2015-08-15  4:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 19:42 [Bug cli/12444] New: " mjw at redhat dot com
2011-01-26 19:50 ` [Bug cli/12444] " mjw at redhat dot com
2011-10-10 12:30 ` aburgess at broadcom dot com
2011-10-10 12:43 ` aburgess at broadcom dot com
2013-10-24  4:15 ` a3at.mail at gmail dot com
2015-08-15  4:53 ` xdje42 at gmail dot com [this message]

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-12444-4717-NvV4N4DMOx@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).