public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/10633] std::string pretty printer should respect 'print elements' limit
Date: Mon, 21 Sep 2009 09:40:00 -0000 [thread overview]
Message-ID: <20090921094017.15912.qmail@sourceware.org> (raw)
In-Reply-To: <20090912003708.10633.ppluzhnikov@google.com>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2009-09-21 09:40 -------
Subject: Bug 10633
CVSROOT: /cvs/src
Module name: src
Changes by: pmuldoon@sourceware.org 2009-09-21 09:39:53
Modified files:
gdb : ChangeLog c-lang.c
gdb/testsuite : ChangeLog
gdb/testsuite/gdb.python: py-prettyprint.exp
Log message:
2009-09-21 Phil Muldoon <pmuldoon@redhat.com>
PR python/10633
* c-lang.c (c_printstr): Do not loop past options->print_max when
iterating with wchar_iterate.
2009-09-21 Phil Muldoon <pmuldoon@redhat.com>
PR python/10633
* gdb.python/py-prettyprint.exp (gdb_py_test_silent_cmd): New
Function.
(run_lang_tests): Add print elements test.
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.10890&r2=1.10891
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/c-lang.c.diff?cvsroot=src&r1=1.75&r2=1.76
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/testsuite/ChangeLog.diff?cvsroot=src&r1=1.1962&r2=1.1963
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.python/py-prettyprint.exp.diff?cvsroot=src&r1=1.1&r2=1.2
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10633
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-09-21 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 0:37 [Bug python/10633] New: " ppluzhnikov at google dot com
2009-09-14 9:20 ` [Bug python/10633] " pmuldoon at redhat dot com
2009-09-14 11:47 ` pmuldoon at redhat dot com
2009-09-14 12:41 ` pmuldoon at redhat dot com
2009-09-14 13:15 ` pmuldoon at redhat dot com
2009-09-15 13:29 ` pmuldoon at redhat dot com
2009-09-15 13:30 ` pmuldoon at redhat dot com
2009-09-21 9:40 ` cvs-commit at gcc dot gnu dot org [this message]
2009-09-21 10:25 ` cvs-commit at gcc dot gnu dot org
2009-09-21 11:11 ` pmuldoon at redhat dot com
2009-09-21 11:12 ` 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=20090921094017.15912.qmail@sourceware.org \
--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).