public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/18350] Invalid free() in tui_check_register_values() [Heap Corruption]
Date: Thu, 02 Jul 2015 13:09:00 -0000	[thread overview]
Message-ID: <bug-18350-4717-qXrEF8fmZw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18350-4717@http.sourceware.org/bugzilla/>

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

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |palves at redhat dot com
         Resolution|---                         |WORKSFORME

--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
There were fixes to memory management is this area to fix a similar crash.  I
tried to reproduce this, but couldn't.  Ithink this is fixed now.

Please reopen if you see it happen with current master (soon to be 7.10).  If
you see it happen, running gdb under Valgrind will most likely point directly
at the culprit.

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


      parent reply	other threads:[~2015-07-02 13:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 21:13 [Bug tui/18350] New: " proto0x0 at gmail dot com
2015-04-28 21:25 ` [Bug tui/18350] " proto0x0 at gmail dot com
2015-07-02 13:09 ` palves at redhat 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-18350-4717-qXrEF8fmZw@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).