public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/16196] lazy string vs "print elements" Date: Fri, 22 Nov 2013 22:01:00 -0000 [thread overview] Message-ID: <bug-16196-4717-BKgtKdSDmn@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16196-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=16196 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via f380848e84613364a17008f04e91bfef09eaf158 (commit) from c0621699ffdbeea387ea37a90258939540b26424 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f380848e84613364a17008f04e91bfef09eaf158 commit f380848e84613364a17008f04e91bfef09eaf158 Author: Sterling Augustine <saugustine@google.com> Date: Fri Nov 22 13:55:32 2013 -0800 2013-11-22 Sterling Augustine <saugustine@google.com> PR gdb/16196: * valprint.c (read_string): Set new variable fetchlen based on fetchlimit and size. Use it in call to partial_memory_read. Update comment. ----------------------------------------------------------------------- Summary of changes: gdb/ChangeLog | 7 +++++++ gdb/valprint.c | 18 +++++++++++------- 2 files changed, 18 insertions(+), 7 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-11-22 22:01 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-20 21:28 [Bug python/16196] New: " dje at google dot com 2013-11-20 21:29 ` [Bug python/16196] " dje at google dot com 2013-11-22 20:32 ` dje at google dot com 2013-11-22 22:01 ` cvs-commit at gcc dot gnu.org [this message] 2013-11-22 22:25 ` cvs-commit at gcc dot gnu.org 2013-11-23 7:20 ` asmwarrior at gmail dot com 2013-11-24 7:33 ` asmwarrior at gmail dot com 2023-12-09 13:04 ` ssbssa at sourceware dot org 2024-11-18 19:47 ` tromey 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-16196-4717-BKgtKdSDmn@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: linkBe 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).