public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/11380] print formats (/FMT) do not invoke Python pretty printers
Date: Tue, 19 Aug 2014 16:31:00 -0000	[thread overview]
Message-ID: <bug-11380-4717-08mpZW25S6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11380-4717@http.sourceware.org/bugzilla/>

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

dje at google dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |dje at google dot com
         Resolution|---                         |WORKSFORME

--- Comment #1 from dje at google dot com ---
I guess this has been fixed since, because I can't repro this.
[btw, I'm assuming there's a typo in the repro instructions:
Is it possible the first "p /f the_semaphore->Object.id" was actually "p
the_semaphore.Object" ?]

>From the gdb build tree, after running the py-prettyprint.exp testcase:

bash$ make run
(gdb) file testsuite/gdb.python/py-prettyprint
(gdb) source ../src/gdb/testsuite/gdb.python/py-prettyprint.py
(gdb) start
[...]
264       string x = make_string ("this is x");
(gdb) n
265       zzz_type c = make_container ("container");
(gdb) 
266       zzz_type c2 = make_container ("container2");
(gdb) 
267       const struct string_repr cstring = { { "const string" } };
(gdb) 
277       nstype.elements = narray;
(gdb) 
278       nstype.len = 0;
(gdb) 
280       me.s = "blah";
(gdb) 
282       init_ss(&ss, 1, 2);
(gdb) 
283       init_ss(ssa+0, 3, 4);
(gdb) 
284       init_ss(ssa+1, 5, 6);
(gdb) 
285       memset (&nullstr, 0, sizeof nullstr);
(gdb) p ss
$1 = a=< a=<1> b=<0x7fffffffe670>> b=< a=<2> b=<0x7fffffffe680>>
(gdb) p/x ss
$2 = a=< a=<1> b=<0x7fffffffe670>> b=< a=<2> b=<0x7fffffffe680>>
(gdb) p/r ss
$3 = {
  a = {
    a = 0x1,
    b = 0x7fffffffe670
  },
  b = {
    a = 0x2,
    b = 0x7fffffffe680
  }
}
(gdb)

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


       reply	other threads:[~2014-08-19 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11380-4717@http.sourceware.org/bugzilla/>
2014-08-19 16:31 ` dje at google dot com [this message]
2010-03-15 22:49 [Bug python/11380] New: " chrisj at rtems dot org
2010-04-19  7:25 ` [Bug python/11380] " pmuldoon at redhat 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-11380-4717-08mpZW25S6@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).