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/18438] PyExc_MemoryError != gdbpy_gdb_memory_error
Date: Tue, 26 May 2015 23:15:00 -0000	[thread overview]
Message-ID: <bug-18438-4717-rfPN9UsoLC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18438-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Doug Evans <devans@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4ea6efe9365f8a87723fe01a2dd8ddf5cdec1498

commit 4ea6efe9365f8a87723fe01a2dd8ddf5cdec1498
Author: Doug Evans <dje@google.com>
Date:   Tue May 26 16:13:04 2015 -0700

    PR python/18438

    gdb/ChangeLog:

        * python/py-lazy-string.c (stpy_convert_to_value): Use
        gdbpy_gdb_memory_error not PyExc_MemoryError.
        (gdbpy_create_lazy_string_object): Ditto.

    gdb/testsuite/ChangeLog:

        * gdb.python/py-lazy-string.c: New file.
        * gdb.python/py-lazy-string.exp: New file.
        * gdb.python/py-prettyprint.c (lazystring) <len>: New member.
        (main): Update.  Add estring3.
        * gdb.python/py-prettyprint.exp: Add tests for strings at address 0.
        * gdb.python/py-prettyprint.py (pp_ls): Handle length.

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


  reply	other threads:[~2015-05-26 23:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 21:32 [Bug python/18438] New: " dje at google dot com
2015-05-26 23:15 ` cvs-commit at gcc dot gnu.org [this message]
2015-05-26 23:17 ` [Bug python/18438] " dje at google 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-18438-4717-rfPN9UsoLC@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).